Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5770cf22c9968d6454483fd3f6623ca0c1da429edd229b07b853144efee62a2d

Tx prefix hash: ec626f8b5e49369192ad67e697b1f1aa6c49acc0a0d6cff60e4d5e8bc0698ea2
Tx public key: d4d87bd80c7fdd10e1c985cb064de83e97a8ff516a4156d03abb90d31d380bc7
Timestamp: 1718708337 Timestamp [UCT]: 2024-06-18 10:58:57 Age [y:d:h:m:s]: 00:280:20:52:18
Block: 1046846 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200687 RingCT/type: yes/0
Extra: 01d4d87bd80c7fdd10e1c985cb064de83e97a8ff516a4156d03abb90d31d380bc702110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e7fec94ea6988f0418ffaa02871935bfbc1f71caa391a2da8e23a61779ed730 0.600000000000 1516665 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": 1046856, "vin": [ { "gen": { "height": 1046846 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e7fec94ea6988f0418ffaa02871935bfbc1f71caa391a2da8e23a61779ed730" } } ], "extra": [ 1, 212, 216, 123, 216, 12, 127, 221, 16, 225, 201, 133, 203, 6, 77, 232, 62, 151, 168, 255, 81, 106, 65, 86, 208, 58, 187, 144, 211, 29, 56, 11, 199, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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