Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1af7fbc9588a1efcaf492dfe45507ab87f9de1094236b4aef041419f1f5a7a87

Tx prefix hash: b2b65d2c273ba8550de42003a80980c56cee638bddc73662ba5803f58a56e8e2
Tx public key: 266e1662eeea2cfc5a7e4f0f056231cee125ce6e8f3d5e90287d99758504cd4f
Timestamp: 1741409435 Timestamp [UCT]: 2025-03-08 04:50:35 Age [y:d:h:m:s]: 00:257:23:36:20
Block: 1234591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182109 RingCT/type: yes/0
Extra: 01266e1662eeea2cfc5a7e4f0f056231cee125ce6e8f3d5e90287d99758504cd4f021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f694afe6d33b03a469a0369225727aaa8a0622e0c334b0611e887c632506034 0.600000000000 1721522 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": 1234601, "vin": [ { "gen": { "height": 1234591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f694afe6d33b03a469a0369225727aaa8a0622e0c334b0611e887c632506034" } } ], "extra": [ 1, 38, 110, 22, 98, 238, 234, 44, 252, 90, 126, 79, 15, 5, 98, 49, 206, 225, 37, 206, 110, 143, 61, 94, 144, 40, 125, 153, 117, 133, 4, 205, 79, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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