Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 182a39289b5c016c145e97fd70cbb254f4284fb05fb0698e93b86eeb3509c84b

Tx prefix hash: 0ff4ab3872d6f4e169fee959cd1aaafa4d36a14efb6cd59a2f1a80090a31eec2
Tx public key: cd2cc29ccd690d51fd1ff3937383c1ae3eb53c00c6a3bb7058e88417cd5d3fd7
Timestamp: 1739103898 Timestamp [UCT]: 2025-02-09 12:24:58 Age [y:d:h:m:s]: 00:332:02:33:55
Block: 1215505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235186 RingCT/type: yes/0
Extra: 01cd2cc29ccd690d51fd1ff3937383c1ae3eb53c00c6a3bb7058e88417cd5d3fd7021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd604aa543a95b3e7907ddebc8bf41446a530db72417e5d423223e9a0f9433c5 0.600000000000 1702304 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": 1215515, "vin": [ { "gen": { "height": 1215505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd604aa543a95b3e7907ddebc8bf41446a530db72417e5d423223e9a0f9433c5" } } ], "extra": [ 1, 205, 44, 194, 156, 205, 105, 13, 81, 253, 31, 243, 147, 115, 131, 193, 174, 62, 181, 60, 0, 198, 163, 187, 112, 88, 232, 132, 23, 205, 93, 63, 215, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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