Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 3a365d890a95fb083c87a8b103a6be7a73c5268ca081a7e6d70e8befbac161f2

Tx prefix hash: 3ba7ce6913eece412bca399a0a2a9278deb80a2f97fc23bb7ab179ca9713cfad
Tx public key: caccdb1cd20984912f0fb792bde9547fdb3acc505a10f9ba6e6897399c7439b2
Timestamp: 1710698084 Timestamp [UCT]: 2024-03-17 17:54:44 Age [y:d:h:m:s]: 00:187:20:31:42
Block: 980456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134542 RingCT/type: yes/0
Extra: 01caccdb1cd20984912f0fb792bde9547fdb3acc505a10f9ba6e6897399c7439b20211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31986da53a5fe4ffc41bf83c66be77e3637a7c7b5bd4cb1b6aee850c67b6e2d0 0.600000000000 1440523 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 980466, "vin": [ { "gen": { "height": 980456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31986da53a5fe4ffc41bf83c66be77e3637a7c7b5bd4cb1b6aee850c67b6e2d0" } } ], "extra": [ 1, 202, 204, 219, 28, 210, 9, 132, 145, 47, 15, 183, 146, 189, 233, 84, 127, 219, 58, 204, 80, 90, 16, 249, 186, 110, 104, 151, 57, 156, 116, 57, 178, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8