Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 335b63f3e06def3bb8003edd3c0c8495906a1bab9a31eea58745d502c12bb525

Tx prefix hash: f27cbeb49495068b7e69637d9c363c41af5efe1c6594f838ec1499500103a651
Tx public key: b3873ac4c079bad426162a2ace1aa8e4dd4397d064af854a7f348cc5e718c86e
Timestamp: 1759605982 Timestamp [UCT]: 2025-10-04 19:26:22 Age [y:d:h:m:s]: 00:052:19:24:49
Block: 1382788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37816 RingCT/type: yes/0
Extra: 01b3873ac4c079bad426162a2ace1aa8e4dd4397d064af854a7f348cc5e718c86e021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37a49ee4b6a012344f4b5e6dd049e29f7b2a709a1e019c93086593fb9b13551b 0.600000000000 1870931 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": 1382798, "vin": [ { "gen": { "height": 1382788 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37a49ee4b6a012344f4b5e6dd049e29f7b2a709a1e019c93086593fb9b13551b" } } ], "extra": [ 1, 179, 135, 58, 196, 192, 121, 186, 212, 38, 22, 42, 42, 206, 26, 168, 228, 221, 67, 151, 208, 100, 175, 133, 74, 127, 52, 140, 197, 231, 24, 200, 110, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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