Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd32b2b60aafc4a92428a6a67bb2b39c1d5efac44c9f4dc76c6980ec3fdd7d4f

Tx prefix hash: b0442b70017adad71be14778e60b57b06e893f64f3055985a9faf80e70bb3215
Tx public key: aa9cd8e770621951cc7f935ce668f0b68c9aaa6988d351ab269c4bb8130a7a6b
Timestamp: 1713135771 Timestamp [UCT]: 2024-04-14 23:02:51 Age [y:d:h:m:s]: 01:232:01:52:53
Block: 1000631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 424573 RingCT/type: yes/0
Extra: 01aa9cd8e770621951cc7f935ce668f0b68c9aaa6988d351ab269c4bb8130a7a6b02110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbf470f4c793923748de439dff37b815a739dc5e7fa1d9e9fde4469741024c84 0.600000000000 1461129 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": 1000641, "vin": [ { "gen": { "height": 1000631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbf470f4c793923748de439dff37b815a739dc5e7fa1d9e9fde4469741024c84" } } ], "extra": [ 1, 170, 156, 216, 231, 112, 98, 25, 81, 204, 127, 147, 92, 230, 104, 240, 182, 140, 154, 170, 105, 136, 211, 81, 171, 38, 156, 75, 184, 19, 10, 122, 107, 2, 17, 0, 0, 0, 12, 89, 218, 211, 245, 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