Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77f8b60c97d5e05892b370888fb10f02caeda64f3870b3f83543e613119d6aaa

Tx prefix hash: e64c254194b08d64dd7f01d46b7385749cba45d7ac9813896928bc890032b3a6
Tx public key: e16359df1d9ab7d0116a79083e57a08fdfe7ae53ae60a826b90b8ed676a8af6e
Timestamp: 1723122824 Timestamp [UCT]: 2024-08-08 13:13:44 Age [y:d:h:m:s]: 00:313:12:06:14
Block: 1083443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223881 RingCT/type: yes/0
Extra: 01e16359df1d9ab7d0116a79083e57a08fdfe7ae53ae60a826b90b8ed676a8af6e021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0d8fcb01005b7513d15c02d45c2de1080166330e90f02741a3cddc1461abcfd 0.600000000000 1557366 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": 1083453, "vin": [ { "gen": { "height": 1083443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0d8fcb01005b7513d15c02d45c2de1080166330e90f02741a3cddc1461abcfd" } } ], "extra": [ 1, 225, 99, 89, 223, 29, 154, 183, 208, 17, 106, 121, 8, 62, 87, 160, 143, 223, 231, 174, 83, 174, 96, 168, 38, 185, 11, 142, 214, 118, 168, 175, 110, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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