Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b07961ce81d81bc8326548d9f26d9cef0eed47b9f2bd761df81120d1304df18

Tx prefix hash: 02f91f13b6e1b9b0d93af764eeda704bbd562bd5fe4f8872dde74fdd0a274e81
Tx public key: 7c6e7bd31a79226aad6bedd9ae23f6d0cec98e33fee3c08fcdec57b3394a6ef0
Timestamp: 1677060985 Timestamp [UCT]: 2023-02-22 10:16:25 Age [y:d:h:m:s]: 02:115:19:45:51
Block: 702448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 604308 RingCT/type: yes/0
Extra: 017c6e7bd31a79226aad6bedd9ae23f6d0cec98e33fee3c08fcdec57b3394a6ef002110000000674b6d784000000000000000000

1 output(s) for total of 2.887341052000 dcy

stealth address amount amount idx
00: 97aa16a51749ac5540afae4bc5af3a48ff42a0bf89730284298cce63c5010dc2 2.887341052000 1145955 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": 702458, "vin": [ { "gen": { "height": 702448 } } ], "vout": [ { "amount": 2887341052, "target": { "key": "97aa16a51749ac5540afae4bc5af3a48ff42a0bf89730284298cce63c5010dc2" } } ], "extra": [ 1, 124, 110, 123, 211, 26, 121, 34, 106, 173, 107, 237, 217, 174, 35, 246, 208, 206, 201, 142, 51, 254, 227, 192, 143, 205, 236, 87, 179, 57, 74, 110, 240, 2, 17, 0, 0, 0, 6, 116, 182, 215, 132, 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