Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c1a0d3fcb8c9e9e88c4352c11495d93baa3334983b5d4cd784e636edc166e84

Tx prefix hash: 779e81a99acca85ed55e86b6fb6aaf9bea59faf7b8b0c92d8999a95412792a69
Tx public key: 33ca57a232a692e594ba35cfa2c123b08ba8157cb871cfdf57eddc37df4dbc55
Timestamp: 1751846151 Timestamp [UCT]: 2025-07-06 23:55:51 Age [y:d:h:m:s]: 00:128:11:14:55
Block: 1320257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90216 RingCT/type: yes/0
Extra: 0133ca57a232a692e594ba35cfa2c123b08ba8157cb871cfdf57eddc37df4dbc5502110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08b1ffae23f92fa7d4a9cfdb87e0c6999c5cbc1d9b26451be8dccfece5628636 0.600000000000 1807954 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": 1320267, "vin": [ { "gen": { "height": 1320257 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08b1ffae23f92fa7d4a9cfdb87e0c6999c5cbc1d9b26451be8dccfece5628636" } } ], "extra": [ 1, 51, 202, 87, 162, 50, 166, 146, 229, 148, 186, 53, 207, 162, 193, 35, 176, 139, 168, 21, 124, 184, 113, 207, 223, 87, 237, 220, 55, 223, 77, 188, 85, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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