Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 987a2704fb42f8e475ade3fa6bf37c1d4af7943d02e53d3d061696c10ba19ae9

Tx prefix hash: d75d9c676991222ba52e82d3ae3b10eefe605b160672d70021153170a02f5ed1
Tx public key: cf9da8bef9a4bce751160f3f729c8ed3253d83c77da50b4ccfe31c922d675ba1
Timestamp: 1759039524 Timestamp [UCT]: 2025-09-28 06:05:24 Age [y:d:h:m:s]: 00:102:11:41:12
Block: 1378084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73405 RingCT/type: yes/0
Extra: 01cf9da8bef9a4bce751160f3f729c8ed3253d83c77da50b4ccfe31c922d675ba1021100000004a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e98ae70a47107e274ff4af8ca4a0e88b67ee80bb93b4571a1166ec48ca18c95 0.600000000000 1866179 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": 1378094, "vin": [ { "gen": { "height": 1378084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e98ae70a47107e274ff4af8ca4a0e88b67ee80bb93b4571a1166ec48ca18c95" } } ], "extra": [ 1, 207, 157, 168, 190, 249, 164, 188, 231, 81, 22, 15, 63, 114, 156, 142, 211, 37, 61, 131, 199, 125, 165, 11, 76, 207, 227, 28, 146, 45, 103, 91, 161, 2, 17, 0, 0, 0, 4, 165, 220, 205, 121, 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