Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d6784c162aa2b8fa9a281683340e530a7fdfe41af5c4baea66808b6f671d984

Tx prefix hash: e6c90304f32915c2ff769c3b42f646c8f4e0bd6cbd672e0bc9fe828ded3c61d0
Tx public key: 71334fb0d95d6569b449ff5bc8b419c5469a09a22c17fba155ee7a8b276ec6dd
Timestamp: 1765137701 Timestamp [UCT]: 2025-12-07 20:01:41 Age [y:d:h:m:s]: 00:014:14:02:14
Block: 1428635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 10438 RingCT/type: yes/0
Extra: 0171334fb0d95d6569b449ff5bc8b419c5469a09a22c17fba155ee7a8b276ec6dd02090000000618364d7500

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 649deef6056845f0e2e302e153848e04acee5f6c7f59c454167298ee378ec4f6 0.600000000000 1917356 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": 1428645, "vin": [ { "gen": { "height": 1428635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "649deef6056845f0e2e302e153848e04acee5f6c7f59c454167298ee378ec4f6" } } ], "extra": [ 1, 113, 51, 79, 176, 217, 93, 101, 105, 180, 73, 255, 91, 200, 180, 25, 197, 70, 154, 9, 162, 44, 23, 251, 161, 85, 238, 122, 139, 39, 110, 198, 221, 2, 9, 0, 0, 0, 6, 24, 54, 77, 117, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8