Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf212fd15a37b86d8d6cbf9c022ca7a5144d43fb10dd7d65b61c388e3edbeec4

Tx prefix hash: 9c2640896474e17769a6c44995693f00c062961dd58bfda966e5bc88870f6ec9
Tx public key: 28cb10c03c0477bb1c281325f3113f8c022b4695ea00b621a3e32a549facb3c5
Timestamp: 1754157613 Timestamp [UCT]: 2025-08-02 18:00:13 Age [y:d:h:m:s]: 00:021:01:31:13
Block: 1338892 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14009 RingCT/type: yes/0
Extra: 0128cb10c03c0477bb1c281325f3113f8c022b4695ea00b621a3e32a549facb3c502110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b81bbc80fbab9e76502a800bd226a77521edbfb19e0ac95218ac6705b2bacaae 0.600000000000 1826703 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": 1338902, "vin": [ { "gen": { "height": 1338892 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b81bbc80fbab9e76502a800bd226a77521edbfb19e0ac95218ac6705b2bacaae" } } ], "extra": [ 1, 40, 203, 16, 192, 60, 4, 119, 187, 28, 40, 19, 37, 243, 17, 63, 140, 2, 43, 70, 149, 234, 0, 182, 33, 163, 227, 42, 84, 159, 172, 179, 197, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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