Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2452496f21579d47ddae4efaad08b27c05602f91d83be809cb57300a74756c2f

Tx prefix hash: 68935499b072b5035688739e45595432a85d6d4f78a379d65cb91c0eba73a96b
Tx public key: 1c19b100adb5c9a6889a4f953dc5264f8d1e9afc5219ce105529cb7db4fbd73b
Timestamp: 1729126738 Timestamp [UCT]: 2024-10-17 00:58:58 Age [y:d:h:m:s]: 00:147:10:07:09
Block: 1133225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105141 RingCT/type: yes/0
Extra: 011c19b100adb5c9a6889a4f953dc5264f8d1e9afc5219ce105529cb7db4fbd73b0211000000073cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98e49e78e0852938ad74f62d40ad45416e28d743e3d9154831d7a080bc98d385 0.600000000000 1616302 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": 1133235, "vin": [ { "gen": { "height": 1133225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98e49e78e0852938ad74f62d40ad45416e28d743e3d9154831d7a080bc98d385" } } ], "extra": [ 1, 28, 25, 177, 0, 173, 181, 201, 166, 136, 154, 79, 149, 61, 197, 38, 79, 141, 30, 154, 252, 82, 25, 206, 16, 85, 41, 203, 125, 180, 251, 215, 59, 2, 17, 0, 0, 0, 7, 60, 208, 252, 6, 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