Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd96d3a6004821a9ff6242080c5a43e6dc0303f20086e2676bdbdff3681ee4d0

Tx prefix hash: cd0590915cfb0b40d860de242b0b9a79ad2df9f09cfc3a46bf17e08c273c1506
Tx public key: 5288a3386b2d8ee4e3bb49e6b1e3f174d603e4b7a5d4a76653af7061604b3ee7
Timestamp: 1728531445 Timestamp [UCT]: 2024-10-10 03:37:25 Age [y:d:h:m:s]: 00:216:11:32:59
Block: 1128286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154545 RingCT/type: yes/0
Extra: 015288a3386b2d8ee4e3bb49e6b1e3f174d603e4b7a5d4a76653af7061604b3ee702110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd12ad262c7b89f4d2f7c2b299121e64379eb2c9f0e780bbb86d3d9393338b60 0.600000000000 1611103 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": 1128296, "vin": [ { "gen": { "height": 1128286 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd12ad262c7b89f4d2f7c2b299121e64379eb2c9f0e780bbb86d3d9393338b60" } } ], "extra": [ 1, 82, 136, 163, 56, 107, 45, 142, 228, 227, 187, 73, 230, 177, 227, 241, 116, 214, 3, 228, 183, 165, 212, 167, 102, 83, 175, 112, 97, 96, 75, 62, 231, 2, 17, 0, 0, 0, 3, 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