Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9deecdcaf67f3b197fac2c989f70271f6f57e9d0d619e0ed4df8c6893f42595

Tx prefix hash: e1db561b756ddbc3641749307db22b3c5e0182f067f516cc893211ff00e6e58d
Tx public key: 1a533bcbb72fdd2ab4d37e1965c2691c6399ad0badae8dad0b238af5063d3627
Timestamp: 1765021539 Timestamp [UCT]: 2025-12-06 11:45:39 Age [y:d:h:m:s]: 00:054:17:39:34
Block: 1427669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39017 RingCT/type: yes/0
Extra: 011a533bcbb72fdd2ab4d37e1965c2691c6399ad0badae8dad0b238af5063d3627021100000009d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6352ff6ff7b9309ee4d0e54414fbf46a9340a34f7f4f35ff77ff5e4b727f1aa 0.600000000000 1916372 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": 1427679, "vin": [ { "gen": { "height": 1427669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6352ff6ff7b9309ee4d0e54414fbf46a9340a34f7f4f35ff77ff5e4b727f1aa" } } ], "extra": [ 1, 26, 83, 59, 203, 183, 47, 221, 42, 180, 211, 126, 25, 101, 194, 105, 28, 99, 153, 173, 11, 173, 174, 141, 173, 11, 35, 138, 245, 6, 61, 54, 39, 2, 17, 0, 0, 0, 9, 214, 225, 157, 124, 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