Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fddb6156ead7cc929c495bc04b499759c0b74da6daeaf3d3d272f93957da22e

Tx prefix hash: 52a53c939690a1f9fc5e40cb8759af4c4a35fb7ed2ba82838eab92ef7785ee7b
Tx public key: 2db852d9861f573332293e61c4c6ef10641e66c17d751609c51e02ebd0ca8b4b
Timestamp: 1738218323 Timestamp [UCT]: 2025-01-30 06:25:23 Age [y:d:h:m:s]: 00:320:18:07:56
Block: 1208167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227049 RingCT/type: yes/0
Extra: 012db852d9861f573332293e61c4c6ef10641e66c17d751609c51e02ebd0ca8b4b0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69381ab4ffd60569170d21a2462dbaa01033f19ba7ebfb8a33d270c40ee4b8b2 0.600000000000 1694896 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": 1208177, "vin": [ { "gen": { "height": 1208167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69381ab4ffd60569170d21a2462dbaa01033f19ba7ebfb8a33d270c40ee4b8b2" } } ], "extra": [ 1, 45, 184, 82, 217, 134, 31, 87, 51, 50, 41, 62, 97, 196, 198, 239, 16, 100, 30, 102, 193, 125, 117, 22, 9, 197, 30, 2, 235, 208, 202, 139, 75, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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