Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5278e6b3ec5876f168a8e33350e85b9e0a9a22eb390d84d2376542fe72f7814d

Tx prefix hash: 172739bf7e0ad0857801b0ff6d317ff3275d803c1a29f5a6c9c5c576ad0e9208
Tx public key: 6eaf450a981efbee30e0a73b23ffabc36b5ca68669ed7788fab4fa6d0e546fb2
Timestamp: 1735258984 Timestamp [UCT]: 2024-12-27 00:23:04 Age [y:d:h:m:s]: 00:088:12:21:03
Block: 1183935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63043 RingCT/type: yes/0
Extra: 016eaf450a981efbee30e0a73b23ffabc36b5ca68669ed7788fab4fa6d0e546fb20211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 131b08ff0f7b90e171a1d7ff2e3772fcfe592e1fdbaf0cbf32a5a10905e5c8e1 0.600000000000 1670384 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": 1183945, "vin": [ { "gen": { "height": 1183935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "131b08ff0f7b90e171a1d7ff2e3772fcfe592e1fdbaf0cbf32a5a10905e5c8e1" } } ], "extra": [ 1, 110, 175, 69, 10, 152, 30, 251, 238, 48, 224, 167, 59, 35, 255, 171, 195, 107, 92, 166, 134, 105, 237, 119, 136, 250, 180, 250, 109, 14, 84, 111, 178, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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