Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 331c7f74b38df6b8c609a3360debc95e29f53e533675a44bb8d4739fee55ee31

Tx prefix hash: 67a81fff77bf4e00045ea9497b16f5f6bfbd5f9e920f70ca9b3589664c688894
Tx public key: 9375d143df41972dd5d09e071d56b624379989559eb8acfcf797a8b1c7035e34
Timestamp: 1747647408 Timestamp [UCT]: 2025-05-19 09:36:48 Age [y:d:h:m:s]: 00:141:17:10:19
Block: 1286227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98923 RingCT/type: yes/0
Extra: 019375d143df41972dd5d09e071d56b624379989559eb8acfcf797a8b1c7035e3402110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74fd86a087a36f94b5692cef7b3fab164a6f505c6d66d707cbfa43b54fd0d336 0.600000000000 1773692 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": 1286237, "vin": [ { "gen": { "height": 1286227 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74fd86a087a36f94b5692cef7b3fab164a6f505c6d66d707cbfa43b54fd0d336" } } ], "extra": [ 1, 147, 117, 209, 67, 223, 65, 151, 45, 213, 208, 158, 7, 29, 86, 182, 36, 55, 153, 137, 85, 158, 184, 172, 252, 247, 151, 168, 177, 199, 3, 94, 52, 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