Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a82da1f1ff84c11efa1cb4fa0162662c20f4d267095f13792de2da60b174d54

Tx prefix hash: 19a45943a5f49e9b352dae4b0198619bcb1368ea47e6287e80e92e0067d08dd9
Tx public key: 4b139b95975d3650a9507969fc4528b3d78b249150de517f89bf1a13cfe6b2c5
Timestamp: 1705768186 Timestamp [UCT]: 2024-01-20 16:29:46 Age [y:d:h:m:s]: 01:095:04:13:54
Block: 939537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329145 RingCT/type: yes/0
Extra: 014b139b95975d3650a9507969fc4528b3d78b249150de517f89bf1a13cfe6b2c502110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f8c4909ffd6269a478c2b741c73cdad63d0505ae77a9f840fbcaed223c06171 0.600000000000 1397645 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": 939547, "vin": [ { "gen": { "height": 939537 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f8c4909ffd6269a478c2b741c73cdad63d0505ae77a9f840fbcaed223c06171" } } ], "extra": [ 1, 75, 19, 155, 149, 151, 93, 54, 80, 169, 80, 121, 105, 252, 69, 40, 179, 215, 139, 36, 145, 80, 222, 81, 127, 137, 191, 26, 19, 207, 230, 178, 197, 2, 17, 0, 0, 0, 10, 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