Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba1ae86b4d24fc87fef5fc3f3c154180a6360f64c419c3b5284f1738b294fb16

Tx prefix hash: 195111545ac71eba62a7d651a5bf88b1e793d4400457c7087beca569ec5f3472
Tx public key: 462d0a76d0cc0e7e133b5ddc577c5be28d36d5ddeea2fec914fbf73c9158cfbe
Timestamp: 1714085120 Timestamp [UCT]: 2024-04-25 22:45:20 Age [y:d:h:m:s]: 01:051:09:40:43
Block: 1008506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297606 RingCT/type: yes/0
Extra: 01462d0a76d0cc0e7e133b5ddc577c5be28d36d5ddeea2fec914fbf73c9158cfbe02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 770f1154046a393f0a58a3dcf438121b541a3b989f12208c5d0d5b333e9a7571 0.600000000000 1469978 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": 1008516, "vin": [ { "gen": { "height": 1008506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "770f1154046a393f0a58a3dcf438121b541a3b989f12208c5d0d5b333e9a7571" } } ], "extra": [ 1, 70, 45, 10, 118, 208, 204, 14, 126, 19, 59, 93, 220, 87, 124, 91, 226, 141, 54, 213, 221, 238, 162, 254, 201, 20, 251, 247, 60, 145, 88, 207, 190, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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