Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d682f5242bb4036df6bdeac0d7a802b8dfb68e2397cdad0c1cdc0bdbdd43b618

Tx prefix hash: 5856680d6555b54817e62dee0e9d54d845974474992f219c1008629dea4d32f4
Tx public key: 26d9b39fd0d59bd6fbf1bee74165dafde1bbcdf33727968f530667dae0b523c8
Timestamp: 1710516268 Timestamp [UCT]: 2024-03-15 15:24:28 Age [y:d:h:m:s]: 01:008:23:00:51
Block: 978945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267371 RingCT/type: yes/0
Extra: 0126d9b39fd0d59bd6fbf1bee74165dafde1bbcdf33727968f530667dae0b523c802110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 220cbe31a6609688171be17089b8e2034a455f2e1dae788a2982d619d62d6648 0.600000000000 1438974 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": 978955, "vin": [ { "gen": { "height": 978945 } } ], "vout": [ { "amount": 600000000, "target": { "key": "220cbe31a6609688171be17089b8e2034a455f2e1dae788a2982d619d62d6648" } } ], "extra": [ 1, 38, 217, 179, 159, 208, 213, 155, 214, 251, 241, 190, 231, 65, 101, 218, 253, 225, 187, 205, 243, 55, 39, 150, 143, 83, 6, 103, 218, 224, 181, 35, 200, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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