Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2f3d42b3e23f6f387f749cd9c34f83803e2fc913069215da9f7cd718ef2230d

Tx prefix hash: bc6298fdfbb297a085d47e306d1bda004df5a061ed1350f43be12ec39bfaa434
Tx public key: 7cec6a3ba5d04c82cf92f5649f79a98728dece2c42cebdcde2dbad6614b13f87
Timestamp: 1750583332 Timestamp [UCT]: 2025-06-22 09:08:52 Age [y:d:h:m:s]: 00:149:14:07:54
Block: 1310347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104780 RingCT/type: yes/0
Extra: 017cec6a3ba5d04c82cf92f5649f79a98728dece2c42cebdcde2dbad6614b13f87021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90da223ca64765ae4edb29f0b7ffcdb56589dfc67dbec7c50d0d22153f2ed905 0.600000000000 1797966 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": 1310357, "vin": [ { "gen": { "height": 1310347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90da223ca64765ae4edb29f0b7ffcdb56589dfc67dbec7c50d0d22153f2ed905" } } ], "extra": [ 1, 124, 236, 106, 59, 165, 208, 76, 130, 207, 146, 245, 100, 159, 121, 169, 135, 40, 222, 206, 44, 66, 206, 189, 205, 226, 219, 173, 102, 20, 177, 63, 135, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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