Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af5e822b77b6fd2981bc05221174644bafbb6ddf7e2c8dcc862d1f40822811b3

Tx prefix hash: 2c5c09fb057b54d6d4f907dd75372442be4c285a21888a6d4a6e0916b652132b
Tx public key: da26346db0c49514c4b1b21d6a23bd2e82db21ebfe400f735e63da115440b22b
Timestamp: 1761868869 Timestamp [UCT]: 2025-10-31 00:01:09 Age [y:d:h:m:s]: 00:010:07:30:48
Block: 1401561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7375 RingCT/type: yes/0
Extra: 01da26346db0c49514c4b1b21d6a23bd2e82db21ebfe400f735e63da115440b22b021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a21ff8d8a2eeb62038960a72b3869dc63f9ea4f0b8d40d6f54b4ac86b09f7358 0.600000000000 1889880 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": 1401571, "vin": [ { "gen": { "height": 1401561 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a21ff8d8a2eeb62038960a72b3869dc63f9ea4f0b8d40d6f54b4ac86b09f7358" } } ], "extra": [ 1, 218, 38, 52, 109, 176, 196, 149, 20, 196, 177, 178, 29, 106, 35, 189, 46, 130, 219, 33, 235, 254, 64, 15, 115, 94, 99, 218, 17, 84, 64, 178, 43, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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