Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e795a43a0e1124d54cce01f4f5c93f3bfe62bc00ba82c3ff4e00b0553cc620a3

Tx prefix hash: dd41564f90781bf6ec75dcff0499fab89d46ab00cc0ce3127de4944f0f08b6ef
Tx public key: 5989f3f157a3af21dd5ee7cee2eebdbb4f77ec8415613ef7e6ce3e564149f21c
Timestamp: 1715194310 Timestamp [UCT]: 2024-05-08 18:51:50 Age [y:d:h:m:s]: 01:029:15:33:09
Block: 1017729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282125 RingCT/type: yes/0
Extra: 015989f3f157a3af21dd5ee7cee2eebdbb4f77ec8415613ef7e6ce3e564149f21c02110000000b0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c035d5f798b4e2b2f14d2b0d011277e2199bc60bd37457bc8c2c2e6ce3a4433 0.600000000000 1481514 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": 1017739, "vin": [ { "gen": { "height": 1017729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c035d5f798b4e2b2f14d2b0d011277e2199bc60bd37457bc8c2c2e6ce3a4433" } } ], "extra": [ 1, 89, 137, 243, 241, 87, 163, 175, 33, 221, 94, 231, 206, 226, 238, 189, 187, 79, 119, 236, 132, 21, 97, 62, 247, 230, 206, 62, 86, 65, 73, 242, 28, 2, 17, 0, 0, 0, 11, 0, 17, 5, 91, 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