Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b42a0f1029d19de287e9100cb917310a655712025c0705a7618780c5476b6b00

Tx prefix hash: 45a750445f91ecc584cff8edc4df5da5cb77a350a9d1796abdbf50b52e0c215b
Tx public key: badf9b8c839e7c62094b19d5526b1873afe3173a66f4733bbbd2bc9a483eb482
Timestamp: 1737058219 Timestamp [UCT]: 2025-01-16 20:10:19 Age [y:d:h:m:s]: 00:155:02:25:02
Block: 1198827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110512 RingCT/type: yes/0
Extra: 01badf9b8c839e7c62094b19d5526b1873afe3173a66f4733bbbd2bc9a483eb4820211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f45e4bb630f1bc8b9e15539c2738dacbe1bc5c63358f1ce53becef1caddf8c5 0.600000000000 1685454 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": 1198837, "vin": [ { "gen": { "height": 1198827 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f45e4bb630f1bc8b9e15539c2738dacbe1bc5c63358f1ce53becef1caddf8c5" } } ], "extra": [ 1, 186, 223, 155, 140, 131, 158, 124, 98, 9, 75, 25, 213, 82, 107, 24, 115, 175, 227, 23, 58, 102, 244, 115, 59, 187, 210, 188, 154, 72, 62, 180, 130, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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