Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db02a8b2969398097a32b23eaf0ccdd30ab0379a31d89afb53bb9bebfa0c151d

Tx prefix hash: 9b6ea7f1fe31e65483aff1761a86117bb3a66a493408ec65534cf3e7990e526a
Tx public key: b3ea6ea7bf1df44d4ec733698a0f9f63a23794195f270456adb8555e2c606fa4
Timestamp: 1699347871 Timestamp [UCT]: 2023-11-07 09:04:31 Age [y:d:h:m:s]: 01:188:08:33:47
Block: 886342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395842 RingCT/type: yes/0
Extra: 01b3ea6ea7bf1df44d4ec733698a0f9f63a23794195f270456adb8555e2c606fa4021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.709873590000 dcy

stealth address amount amount idx
00: 44409a00312f195f8f64ef2002c26f248c2b01953f246875086260a12adc85e0 0.709873590000 1342157 of 0

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": 886352, "vin": [ { "gen": { "height": 886342 } } ], "vout": [ { "amount": 709873590, "target": { "key": "44409a00312f195f8f64ef2002c26f248c2b01953f246875086260a12adc85e0" } } ], "extra": [ 1, 179, 234, 110, 167, 191, 29, 244, 77, 78, 199, 51, 105, 138, 15, 159, 99, 162, 55, 148, 25, 95, 39, 4, 86, 173, 184, 85, 94, 44, 96, 111, 164, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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