Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc6ac0bf3e4b8dd6b9d4790c4a32d89cc6aa830d1db49483d4abdb11a2137897

Tx prefix hash: 766b4155b2d75576945ef0a286524be2e5e4548285690830eb8dfe7fc225adb5
Tx public key: a348139c5885878cba6eced9747145fb1ce0255d5a42c3f6a6bb4e4e5cb17717
Timestamp: 1755804090 Timestamp [UCT]: 2025-08-21 19:21:30 Age [y:d:h:m:s]: 00:047:23:46:06
Block: 1351478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34168 RingCT/type: yes/0
Extra: 01a348139c5885878cba6eced9747145fb1ce0255d5a42c3f6a6bb4e4e5cb177170211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2565b2220d5ac1bcdb26a2ac6b38249b173fa7edda47e61efc077e8cc6bb611b 0.600000000000 1839431 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": 1351488, "vin": [ { "gen": { "height": 1351478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2565b2220d5ac1bcdb26a2ac6b38249b173fa7edda47e61efc077e8cc6bb611b" } } ], "extra": [ 1, 163, 72, 19, 156, 88, 133, 135, 140, 186, 110, 206, 217, 116, 113, 69, 251, 28, 224, 37, 93, 90, 66, 195, 246, 166, 187, 78, 78, 92, 177, 119, 23, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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