Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1dbe2032e9531eec7ba5981aaab288983d8241b087649c930fdca39c597dde27

Tx prefix hash: 35d084c7893eda43d46546f430a621c4a13bbb3445db1389ba63df4d7e52693d
Tx public key: 0271b23c76a8cb3f9efabf02063e62c7a4a97c56771983bba2619eb5d975e52a
Timestamp: 1712767900 Timestamp [UCT]: 2024-04-10 16:51:40 Age [y:d:h:m:s]: 01:226:16:15:51
Block: 997570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420719 RingCT/type: yes/0
Extra: 010271b23c76a8cb3f9efabf02063e62c7a4a97c56771983bba2619eb5d975e52a02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c001fe3d7cd2e3a7f8a413a8db5cb232a271783866539f7ae7d6fc27ae726a1b 0.600000000000 1458004 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": 997580, "vin": [ { "gen": { "height": 997570 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c001fe3d7cd2e3a7f8a413a8db5cb232a271783866539f7ae7d6fc27ae726a1b" } } ], "extra": [ 1, 2, 113, 178, 60, 118, 168, 203, 63, 158, 250, 191, 2, 6, 62, 98, 199, 164, 169, 124, 86, 119, 25, 131, 187, 162, 97, 158, 181, 217, 117, 229, 42, 2, 17, 0, 0, 0, 3, 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