Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2409df8e9befdd3c8714f0223fcb4b92cdc97317f17f20ce9a42aa12bd4a21bd

Tx prefix hash: 0585e29a7c16d9e106d86e235a78eb6a549292b69c34fcefdea5550ae78a9650
Tx public key: 4b3fef1d38fbe96ce5ce91513ad344a87a4e573161a4a1032fa5756c56bcbbf3
Timestamp: 1724018441 Timestamp [UCT]: 2024-08-18 22:00:41 Age [y:d:h:m:s]: 00:224:08:24:35
Block: 1090877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160197 RingCT/type: yes/0
Extra: 014b3fef1d38fbe96ce5ce91513ad344a87a4e573161a4a1032fa5756c56bcbbf302110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52ed8cb9dd1c3d13ab8bb21375e37b4bdc2930e249c65fc74a982be6332c52d1 0.600000000000 1565502 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": 1090887, "vin": [ { "gen": { "height": 1090877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52ed8cb9dd1c3d13ab8bb21375e37b4bdc2930e249c65fc74a982be6332c52d1" } } ], "extra": [ 1, 75, 63, 239, 29, 56, 251, 233, 108, 229, 206, 145, 81, 58, 211, 68, 168, 122, 78, 87, 49, 97, 164, 161, 3, 47, 165, 117, 108, 86, 188, 187, 243, 2, 17, 0, 0, 0, 2, 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