Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89fa9d21777a498cb6e24f33799d34ece1d1fb25940e2ae5e845bc2bd545bef7

Tx prefix hash: 73c3655ce7b713743884390671e67b4495e888d245c8b067d75a2d6a93a47144
Tx public key: 362074d1ba11486b8215ca39e091f474ba223e0a837b60b9da0e034babe9d895
Timestamp: 1718249862 Timestamp [UCT]: 2024-06-13 03:37:42 Age [y:d:h:m:s]: 00:225:20:16:27
Block: 1043051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161572 RingCT/type: yes/0
Extra: 01362074d1ba11486b8215ca39e091f474ba223e0a837b60b9da0e034babe9d8950211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc29c3fee5862257cd28d4f550c6f57991617a432bda9f4c3dbe747ca5b231c2 0.600000000000 1512110 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": 1043061, "vin": [ { "gen": { "height": 1043051 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc29c3fee5862257cd28d4f550c6f57991617a432bda9f4c3dbe747ca5b231c2" } } ], "extra": [ 1, 54, 32, 116, 209, 186, 17, 72, 107, 130, 21, 202, 57, 224, 145, 244, 116, 186, 34, 62, 10, 131, 123, 96, 185, 218, 14, 3, 75, 171, 233, 216, 149, 2, 17, 0, 0, 0, 4, 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