Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ef7264de88f3737c7bfcf2ab2dc2c8a3eed4aeeaba16a9c39f65d23b06fa518

Tx prefix hash: 61f64695f33fc6669fc917d79e3c9e95edac7ff269d3760412874f1b3881e6fe
Tx public key: c7033b2fd30fe52a7238e7262f44bfed57ff7657183add4ba96d2ff5f9221a08
Timestamp: 1749114066 Timestamp [UCT]: 2025-06-05 09:01:06 Age [y:d:h:m:s]: 00:157:19:11:07
Block: 1298383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110451 RingCT/type: yes/0
Extra: 01c7033b2fd30fe52a7238e7262f44bfed57ff7657183add4ba96d2ff5f9221a08021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3cc4498930fb3b6fde9851bd655fb36a5a8a27f6ca3150b875cb37f87354c04 0.600000000000 1785910 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": 1298393, "vin": [ { "gen": { "height": 1298383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3cc4498930fb3b6fde9851bd655fb36a5a8a27f6ca3150b875cb37f87354c04" } } ], "extra": [ 1, 199, 3, 59, 47, 211, 15, 229, 42, 114, 56, 231, 38, 47, 68, 191, 237, 87, 255, 118, 87, 24, 58, 221, 75, 169, 109, 47, 245, 249, 34, 26, 8, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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