Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7bb3ae27dc5344b71ba3eafe0465cbc19d330669c2815d4eb5a4802157ef3ed

Tx prefix hash: 3bc1539857ae1eed045d0b970063c3dadcf48d7100c31ebdcbdab4fa8b522799
Tx public key: ccb445471e924e3badd618633f6c2f47ff5dc9f68eae6da4d2366109e08ed451
Timestamp: 1752802508 Timestamp [UCT]: 2025-07-18 01:35:08 Age [y:d:h:m:s]: 00:159:06:58:14
Block: 1327789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112669 RingCT/type: yes/0
Extra: 01ccb445471e924e3badd618633f6c2f47ff5dc9f68eae6da4d2366109e08ed451021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f7de850a3ff7bbfae6cbb9bbc37537fad548ac543c2f2332cbb65198b453a12 0.600000000000 1815548 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": 1327799, "vin": [ { "gen": { "height": 1327789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f7de850a3ff7bbfae6cbb9bbc37537fad548ac543c2f2332cbb65198b453a12" } } ], "extra": [ 1, 204, 180, 69, 71, 30, 146, 78, 59, 173, 214, 24, 99, 63, 108, 47, 71, 255, 93, 201, 246, 142, 174, 109, 164, 210, 54, 97, 9, 224, 142, 212, 81, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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