Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36bad74174f96a656270163d78eb017b4c3186f6e70c48bf632beb05a3cb5c24

Tx prefix hash: 3120f612dbe9fcf3846c3499a6846b3e86be353c8823499d1bf84ee091f0aa8f
Tx public key: 1cd893716a96a1a2fd0e1a664a93e1ed6d19bf726f39f9efdc42d92720e82a87
Timestamp: 1728209192 Timestamp [UCT]: 2024-10-06 10:06:32 Age [y:d:h:m:s]: 00:241:11:34:53
Block: 1125620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172426 RingCT/type: yes/0
Extra: 011cd893716a96a1a2fd0e1a664a93e1ed6d19bf726f39f9efdc42d92720e82a8702110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7077fbf574be776df45699a359d9eee1a68565058847777b41d5312c6d1d89b7 0.600000000000 1608371 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": 1125630, "vin": [ { "gen": { "height": 1125620 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7077fbf574be776df45699a359d9eee1a68565058847777b41d5312c6d1d89b7" } } ], "extra": [ 1, 28, 216, 147, 113, 106, 150, 161, 162, 253, 14, 26, 102, 74, 147, 225, 237, 109, 25, 191, 114, 111, 57, 249, 239, 220, 66, 217, 39, 32, 232, 42, 135, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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