Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 747d50e2c814e69f0739f447ca1c9022ec25bf663af698784acd690bd8f427d6

Tx prefix hash: 0d0c82ffd1dd4845dff32d1b6c3456b618d0f7bf2aff80dbe1df419ff73b1fb4
Tx public key: 6f5591a63f0f9b1786a633ad882c1cb5f3290b3a3d1072c8d1bb32953aebb657
Timestamp: 1756428774 Timestamp [UCT]: 2025-08-29 00:52:54 Age [y:d:h:m:s]: 00:129:19:24:57
Block: 1356602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92824 RingCT/type: yes/0
Extra: 016f5591a63f0f9b1786a633ad882c1cb5f3290b3a3d1072c8d1bb32953aebb657021100000005ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57dfd382e2d1efc9cb02992649129d424dccb9864aa44ae11d05402e34f1bc0f 0.600000000000 1844611 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": 1356612, "vin": [ { "gen": { "height": 1356602 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57dfd382e2d1efc9cb02992649129d424dccb9864aa44ae11d05402e34f1bc0f" } } ], "extra": [ 1, 111, 85, 145, 166, 63, 15, 155, 23, 134, 166, 51, 173, 136, 44, 28, 181, 243, 41, 11, 58, 61, 16, 114, 200, 209, 187, 50, 149, 58, 235, 182, 87, 2, 17, 0, 0, 0, 5, 173, 121, 72, 208, 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