Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 034998fe047adf3ff83346ed9807b2d42f15e8c02f1b01e4bd929a3b6f9c7568

Tx prefix hash: 1ea5ddecef1f4891bf98b2c12a7487715ba42b7cdc094b19c57c3e78ff82740d
Tx public key: 54dd6d2c78f25ac9844a44c3d271a15d1ce2f925d97d99fd4ca5e54acbe02988
Timestamp: 1681950749 Timestamp [UCT]: 2023-04-20 00:32:29 Age [y:d:h:m:s]: 01:352:03:08:41
Block: 742349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 512941 RingCT/type: yes/0
Extra: 0154dd6d2c78f25ac9844a44c3d271a15d1ce2f925d97d99fd4ca5e54acbe02988021100000004e6d27f9c000000000000000000

1 output(s) for total of 2.129559671000 dcy

stealth address amount amount idx
00: 3e32f8947b665c472ee81d3d5e8a0d89c1fa9f0429ea17cf428e52367e9a6e66 2.129559671000 1189310 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": 742359, "vin": [ { "gen": { "height": 742349 } } ], "vout": [ { "amount": 2129559671, "target": { "key": "3e32f8947b665c472ee81d3d5e8a0d89c1fa9f0429ea17cf428e52367e9a6e66" } } ], "extra": [ 1, 84, 221, 109, 44, 120, 242, 90, 201, 132, 74, 68, 195, 210, 113, 161, 93, 28, 226, 249, 37, 217, 125, 153, 253, 76, 165, 229, 74, 203, 224, 41, 136, 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