Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ef01802fb7539f49201d102c0717122552da80b1bb3336f9b5b590b4a2c253c

Tx prefix hash: c4e2be59abea022d0bdb1490f3323c0475a58b705dcb5418fb7860c73b4916a9
Tx public key: 7e6c00809a4dcd57675c02ec36ccf9d5881f97c7ca79111943d7f9ad1d3efd86
Timestamp: 1726010802 Timestamp [UCT]: 2024-09-10 23:26:42 Age [y:d:h:m:s]: 01:056:18:41:58
Block: 1107391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298984 RingCT/type: yes/0
Extra: 017e6c00809a4dcd57675c02ec36ccf9d5881f97c7ca79111943d7f9ad1d3efd8602110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ab9055ff781fb6ca26c2d314f1cac6099ad909dbbccbf9be445dad3bdf3ebe9 0.600000000000 1585002 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": 1107401, "vin": [ { "gen": { "height": 1107391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ab9055ff781fb6ca26c2d314f1cac6099ad909dbbccbf9be445dad3bdf3ebe9" } } ], "extra": [ 1, 126, 108, 0, 128, 154, 77, 205, 87, 103, 92, 2, 236, 54, 204, 249, 213, 136, 31, 151, 199, 202, 121, 17, 25, 67, 215, 249, 173, 29, 62, 253, 134, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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