Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ff1c9c66b7d383a695cb6e3e41dbba862ba361d3f8d2a834a071cba2cc9c284

Tx prefix hash: 72da843271b09c94bca7830ad42dc7cd65725e6075b8ab70f2232c12af91187c
Tx public key: e876ee181be328c80ba52f2d613b089a9ef57d30608c95cfc1115f2ffdd99e5f
Timestamp: 1762044983 Timestamp [UCT]: 2025-11-02 00:56:23 Age [y:d:h:m:s]: 00:004:21:20:16
Block: 1403001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3504 RingCT/type: yes/0
Extra: 01e876ee181be328c80ba52f2d613b089a9ef57d30608c95cfc1115f2ffdd99e5f0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a87b432501f56588a96a5ad3bf1f43f1b8e65e60089fa7f92c034031daf2d172 0.600000000000 1891328 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": 1403011, "vin": [ { "gen": { "height": 1403001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a87b432501f56588a96a5ad3bf1f43f1b8e65e60089fa7f92c034031daf2d172" } } ], "extra": [ 1, 232, 118, 238, 24, 27, 227, 40, 200, 11, 165, 47, 45, 97, 59, 8, 154, 158, 245, 125, 48, 96, 140, 149, 207, 193, 17, 95, 47, 253, 217, 158, 95, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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