Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e73fc1393113f508d0adf02f6f5dd967da82d1952ac42c7dc79d6156b1644105

Tx prefix hash: 9240189644e6631cafd939973846f9de082cded0215cc0f2a01e051bddb4d2f5
Tx public key: 67d35fc1cf0575e5fa1adf7817661fb16e226c54ef25d8985d7d1a16b2bc9059
Timestamp: 1708946833 Timestamp [UCT]: 2024-02-26 11:27:13 Age [y:d:h:m:s]: 01:108:22:46:28
Block: 965931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338847 RingCT/type: yes/0
Extra: 0167d35fc1cf0575e5fa1adf7817661fb16e226c54ef25d8985d7d1a16b2bc90590211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d5448c85f1209bb2ba56aae88ad7a3a0cfda03e187a56d6a97d9e2a5f117c40 0.600000000000 1425686 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": 965941, "vin": [ { "gen": { "height": 965931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d5448c85f1209bb2ba56aae88ad7a3a0cfda03e187a56d6a97d9e2a5f117c40" } } ], "extra": [ 1, 103, 211, 95, 193, 207, 5, 117, 229, 250, 26, 223, 120, 23, 102, 31, 177, 110, 34, 108, 84, 239, 37, 216, 152, 93, 125, 26, 22, 178, 188, 144, 89, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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