Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1102a9058cf36a204068a74fc315732150863a2f01b9b1ccd39e612400b9384

Tx prefix hash: 87daa7e29d2164658de39b7d6267cfb03f12f6e9fa987303f75d60028d7aa18e
Tx public key: 80e134f69820985eae059d7153e706fcd5ee31abb301fe784ea56b2d8e1e16d3
Timestamp: 1721042667 Timestamp [UCT]: 2024-07-15 11:24:27 Age [y:d:h:m:s]: 00:302:22:39:13
Block: 1066211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216455 RingCT/type: yes/0
Extra: 0180e134f69820985eae059d7153e706fcd5ee31abb301fe784ea56b2d8e1e16d3021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f2a9481e8000eacf096f3a11aaf565cfd8cfaaae73a1d6db6bfad881ef5f7c6 0.600000000000 1536784 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": 1066221, "vin": [ { "gen": { "height": 1066211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f2a9481e8000eacf096f3a11aaf565cfd8cfaaae73a1d6db6bfad881ef5f7c6" } } ], "extra": [ 1, 128, 225, 52, 246, 152, 32, 152, 94, 174, 5, 157, 113, 83, 231, 6, 252, 213, 238, 49, 171, 179, 1, 254, 120, 78, 165, 107, 45, 142, 30, 22, 211, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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