Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87340443fc1c9b49e17c7a969542fe195d95ca64aa6839d322ed5b3f53a69fc5

Tx prefix hash: 9e0adb3811aace775f758bf8d34e04a7f07d1f42feaf5b839bcb65ee18cf415b
Tx public key: bf70af935093ee3f82509ac3e65f047f954fce46d8f504bb3f00e215fe87511e
Timestamp: 1699259863 Timestamp [UCT]: 2023-11-06 08:37:43 Age [y:d:h:m:s]: 01:066:17:25:56
Block: 885609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309095 RingCT/type: yes/0
Extra: 01bf70af935093ee3f82509ac3e65f047f954fce46d8f504bb3f00e215fe87511e021100000009faf35c9c000000000000000000

1 output(s) for total of 0.713854586000 dcy

stealth address amount amount idx
00: 4c7e64b1b3e10da6f5e0becb683a9461d34f0745a8a3e1b21d591614eb874f4e 0.713854586000 1341390 of 0

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": 885619, "vin": [ { "gen": { "height": 885609 } } ], "vout": [ { "amount": 713854586, "target": { "key": "4c7e64b1b3e10da6f5e0becb683a9461d34f0745a8a3e1b21d591614eb874f4e" } } ], "extra": [ 1, 191, 112, 175, 147, 80, 147, 238, 63, 130, 80, 154, 195, 230, 95, 4, 127, 149, 79, 206, 70, 216, 245, 4, 187, 63, 0, 226, 21, 254, 135, 81, 30, 2, 17, 0, 0, 0, 9, 250, 243, 92, 156, 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