Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0933545c179e8f5ab57d79df91460ef5a5cb78ab2be59e7d545fea6159c16bd1

Tx prefix hash: b334cff609b39b70ba6c6369c9c904be5444b4493ce6a981b8bc2ed4423afb70
Tx public key: 9b6839f0b95c67d148c98c874521c0c8e0587c2497fea92c49015bec58f7acdb
Timestamp: 1756138427 Timestamp [UCT]: 2025-08-25 16:13:47 Age [y:d:h:m:s]: 00:134:22:45:06
Block: 1354237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96454 RingCT/type: yes/0
Extra: 019b6839f0b95c67d148c98c874521c0c8e0587c2497fea92c49015bec58f7acdb0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5963c1f724a7d10aa618ffabd9be5c7e7e00437aa24634412fd9a1dddc6c04ce 0.600000000000 1842224 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": 1354247, "vin": [ { "gen": { "height": 1354237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5963c1f724a7d10aa618ffabd9be5c7e7e00437aa24634412fd9a1dddc6c04ce" } } ], "extra": [ 1, 155, 104, 57, 240, 185, 92, 103, 209, 72, 201, 140, 135, 69, 33, 192, 200, 224, 88, 124, 36, 151, 254, 169, 44, 73, 1, 91, 236, 88, 247, 172, 219, 2, 17, 0, 0, 0, 3, 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