Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6e4c4f33c259adab530fb465298d31a492ce07cc9b6ffb6bb32eb96c07e02be

Tx prefix hash: 84e1e3f875fbc72098b0fb58fb963cf53142d4d316319ca5e92ca6ad3638f932
Tx public key: 659f2afc5f097e89b932ac83652b99cc731f509f2449baf567a4968c919d3c67
Timestamp: 1744492313 Timestamp [UCT]: 2025-04-12 21:11:53 Age [y:d:h:m:s]: 00:214:15:14:11
Block: 1260098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151129 RingCT/type: yes/0
Extra: 01659f2afc5f097e89b932ac83652b99cc731f509f2449baf567a4968c919d3c670211000000096c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7f0572a9c08be2259ee0919ca0d7c692788b56a546828e3575ee08156e7249c 0.600000000000 1747249 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": 1260108, "vin": [ { "gen": { "height": 1260098 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7f0572a9c08be2259ee0919ca0d7c692788b56a546828e3575ee08156e7249c" } } ], "extra": [ 1, 101, 159, 42, 252, 95, 9, 126, 137, 185, 50, 172, 131, 101, 43, 153, 204, 115, 31, 80, 159, 36, 73, 186, 245, 103, 164, 150, 140, 145, 157, 60, 103, 2, 17, 0, 0, 0, 9, 108, 152, 170, 61, 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