Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac86f20585185a7a322544f033540f5b9015618ef2e9e0de74dae273de59342f

Tx prefix hash: 172980469f3af2be006e0d8213cdf255954821cb2a9ef244dee59930bcfad45b
Tx public key: 7eb113c5ed9caed274fee90aa703780c9d29e9a2ba3fb6f7b1e986280d5e3276
Timestamp: 1726772573 Timestamp [UCT]: 2024-09-19 19:02:53 Age [y:d:h:m:s]: 00:178:16:28:39
Block: 1113698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127550 RingCT/type: yes/0
Extra: 017eb113c5ed9caed274fee90aa703780c9d29e9a2ba3fb6f7b1e986280d5e327602110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5f5fd1b379e5a738fb5ad9460b67f27f8c57d7d8984503d84f34ad671880901 0.600000000000 1593467 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": 1113708, "vin": [ { "gen": { "height": 1113698 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5f5fd1b379e5a738fb5ad9460b67f27f8c57d7d8984503d84f34ad671880901" } } ], "extra": [ 1, 126, 177, 19, 197, 237, 156, 174, 210, 116, 254, 233, 10, 167, 3, 120, 12, 157, 41, 233, 162, 186, 63, 182, 247, 177, 233, 134, 40, 13, 94, 50, 118, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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