Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a04115b771dc7f5b9c5f4db11b49b327ada2ac141fdc32398edd35d6b5ddb81

Tx prefix hash: c5ed71e30f8e4301166d0aae95351e83466db10363beb65c6362c9340c543044
Tx public key: a490652038d628915cf1782b3a9c0a9737e2ef02e7dc5453b66957d23fb85b72
Timestamp: 1736943809 Timestamp [UCT]: 2025-01-15 12:23:29 Age [y:d:h:m:s]: 00:154:11:23:39
Block: 1197876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110099 RingCT/type: yes/0
Extra: 01a490652038d628915cf1782b3a9c0a9737e2ef02e7dc5453b66957d23fb85b720211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88953d378e55ff96f65b5fe1a0c71276a6fbf2f2602d5c3fa603d5d9c149d47c 0.600000000000 1684493 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": 1197886, "vin": [ { "gen": { "height": 1197876 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88953d378e55ff96f65b5fe1a0c71276a6fbf2f2602d5c3fa603d5d9c149d47c" } } ], "extra": [ 1, 164, 144, 101, 32, 56, 214, 40, 145, 92, 241, 120, 43, 58, 156, 10, 151, 55, 226, 239, 2, 231, 220, 84, 83, 182, 105, 87, 210, 63, 184, 91, 114, 2, 17, 0, 0, 0, 2, 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