Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3a64753951d6398e8e03d1c4a3bffa020b19432631d9555c66f3657a7d7efd9

Tx prefix hash: 191fbd093e9e320f2adfc3ab5a252ec56c913675bbc97c86def6f6f75d055cd7
Tx public key: fed750d3a594a67f46bbb9298639edf9bfdd38fc6e672962f07f1db394e5f2b5
Timestamp: 1687948533 Timestamp [UCT]: 2023-06-28 10:35:33 Age [y:d:h:m:s]: 02:133:02:28:14
Block: 792090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 614858 RingCT/type: yes/0
Extra: 01fed750d3a594a67f46bbb9298639edf9bfdd38fc6e672962f07f1db394e5f2b502110000000175e3f0e9000000000000000000

1 output(s) for total of 1.457059072000 dcy

stealth address amount amount idx
00: 7c5db2b334afbe793291ddcae3c7e34896a469bef8907ef0d36ea273e5c37283 1.457059072000 1242659 of 0

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": 792100, "vin": [ { "gen": { "height": 792090 } } ], "vout": [ { "amount": 1457059072, "target": { "key": "7c5db2b334afbe793291ddcae3c7e34896a469bef8907ef0d36ea273e5c37283" } } ], "extra": [ 1, 254, 215, 80, 211, 165, 148, 166, 127, 70, 187, 185, 41, 134, 57, 237, 249, 191, 221, 56, 252, 110, 103, 41, 98, 240, 127, 29, 179, 148, 229, 242, 181, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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