Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32dc614077c434c0d0b4bebd557bc89f3d9ab33162b3d93e5eb4fe034422c2c1

Tx prefix hash: 9a29da2a7319599f0ad8284de0e2991dca94e078fbdb5e02fcbf5f7de18c40a8
Tx public key: c3fc819cac0a7508b27376b3dda8c926483adafdece6315a468282ed1fa241d5
Timestamp: 1728366044 Timestamp [UCT]: 2024-10-08 05:40:44 Age [y:d:h:m:s]: 00:254:14:29:14
Block: 1126912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181669 RingCT/type: yes/0
Extra: 01c3fc819cac0a7508b27376b3dda8c926483adafdece6315a468282ed1fa241d5021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dcdd6b1ec3086d128e346801bfd4475019ac83b06546bbfd487f8e92ecb33a3e 0.600000000000 1609711 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": 1126922, "vin": [ { "gen": { "height": 1126912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dcdd6b1ec3086d128e346801bfd4475019ac83b06546bbfd487f8e92ecb33a3e" } } ], "extra": [ 1, 195, 252, 129, 156, 172, 10, 117, 8, 178, 115, 118, 179, 221, 168, 201, 38, 72, 58, 218, 253, 236, 230, 49, 90, 70, 130, 130, 237, 31, 162, 65, 213, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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