Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1d55444ab1b16705ac509e9e9c1a7b2eeda267850fcb60eb08443a70b3ca05f

Tx prefix hash: c0ad44b350d5e68fbf8c7b1525543c7b8a73fff2d09764e0ef233b1082046957
Tx public key: 9fd9b6478d94c2a86bdd430897ae70a7fe7f85504693a14f4129d5ed822d7774
Timestamp: 1747574115 Timestamp [UCT]: 2025-05-18 13:15:15 Age [y:d:h:m:s]: 00:257:12:53:42
Block: 1285618 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181684 RingCT/type: yes/0
Extra: 019fd9b6478d94c2a86bdd430897ae70a7fe7f85504693a14f4129d5ed822d77740211000000011f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78f130daed74640fd6e4d19805f6142af18ccb444d9f7b8dd6e57068786dce78 0.600000000000 1773083 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": 1285628, "vin": [ { "gen": { "height": 1285618 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78f130daed74640fd6e4d19805f6142af18ccb444d9f7b8dd6e57068786dce78" } } ], "extra": [ 1, 159, 217, 182, 71, 141, 148, 194, 168, 107, 221, 67, 8, 151, 174, 112, 167, 254, 127, 133, 80, 70, 147, 161, 79, 65, 41, 213, 237, 130, 45, 119, 116, 2, 17, 0, 0, 0, 1, 31, 144, 81, 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