Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b7b6a3acb4278200b3b268f3785e0101bc56c10bb3bf6e831c56bf86165f94b

Tx prefix hash: 88f9f1816404910be7845be007f56a7dfe95ea0b63719b8d469e59a40e3c1c8d
Tx public key: 208ddb66b8fbc3d4b1829c5cc2a5179146f6110251a0d23cdfceee0db9c4976e
Timestamp: 1718667292 Timestamp [UCT]: 2024-06-17 23:34:52 Age [y:d:h:m:s]: 00:277:15:22:34
Block: 1046506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198399 RingCT/type: yes/0
Extra: 01208ddb66b8fbc3d4b1829c5cc2a5179146f6110251a0d23cdfceee0db9c4976e0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8febaded86ff82615fc7a63fd427a434b5080f80b60f13c7f34099ae8232239 0.600000000000 1516321 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": 1046516, "vin": [ { "gen": { "height": 1046506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8febaded86ff82615fc7a63fd427a434b5080f80b60f13c7f34099ae8232239" } } ], "extra": [ 1, 32, 141, 219, 102, 184, 251, 195, 212, 177, 130, 156, 92, 194, 165, 23, 145, 70, 246, 17, 2, 81, 160, 210, 60, 223, 206, 238, 13, 185, 196, 151, 110, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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