Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3ef24dfb6aafdd1a660768a9bf3cc2a804c7d0f132a9f714ebb3c36e236fd2c

Tx prefix hash: 8d40c1d6765d90ea07ecb54c3ad949e72126cec7f6be5471518b74343932bc38
Tx public key: 2b42ca9d1112172ab7e7ee6cb45fddab9ba17e3eee15b96324973b1465d69b83
Timestamp: 1762710649 Timestamp [UCT]: 2025-11-09 17:50:49 Age [y:d:h:m:s]: 00:048:23:12:02
Block: 1408528 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35057 RingCT/type: yes/0
Extra: 012b42ca9d1112172ab7e7ee6cb45fddab9ba17e3eee15b96324973b1465d69b83021100000005df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67f14baca7e92090f1fcb121c95c242751efdd07fd1cec5554a7250a93f0d985 0.600000000000 1896957 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": 1408538, "vin": [ { "gen": { "height": 1408528 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67f14baca7e92090f1fcb121c95c242751efdd07fd1cec5554a7250a93f0d985" } } ], "extra": [ 1, 43, 66, 202, 157, 17, 18, 23, 42, 183, 231, 238, 108, 180, 95, 221, 171, 155, 161, 126, 62, 238, 21, 185, 99, 36, 151, 59, 20, 101, 214, 155, 131, 2, 17, 0, 0, 0, 5, 223, 90, 36, 122, 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