Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fec2451431ae6aef0910a782a98db65ee57166b1f48c3dcc085dfe6d42d6caf

Tx prefix hash: 41da5d9c4f240e77ee1a41e9c4b99c3efbb3afcdc5ef3ff4a18d1d5b86342259
Tx public key: b8364b029e4d665b58b4220ba0fdd116d912e6ebdde8833e478b4abe3cb794cc
Timestamp: 1761950825 Timestamp [UCT]: 2025-10-31 22:47:05 Age [y:d:h:m:s]: 00:007:12:36:15
Block: 1402238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5370 RingCT/type: yes/0
Extra: 01b8364b029e4d665b58b4220ba0fdd116d912e6ebdde8833e478b4abe3cb794cc02110000000425a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ccd0d5cf9cc70b3a0536e39f1d9f59cfdfec50cf4093bdce49ae042472f21fc5 0.600000000000 1890557 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": 1402248, "vin": [ { "gen": { "height": 1402238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ccd0d5cf9cc70b3a0536e39f1d9f59cfdfec50cf4093bdce49ae042472f21fc5" } } ], "extra": [ 1, 184, 54, 75, 2, 158, 77, 102, 91, 88, 180, 34, 11, 160, 253, 209, 22, 217, 18, 230, 235, 221, 232, 131, 62, 71, 139, 74, 190, 60, 183, 148, 204, 2, 17, 0, 0, 0, 4, 37, 163, 90, 15, 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