Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 511fd7f514854e6c5e4e684aac2112063f6dc5b2df82621d8b619a80ca406ab9

Tx prefix hash: b3b0307531179386b8234d6b5a9a48c610440f9357e2989504b599b776c21014
Tx public key: f62e92924b7eeedfa7891a9a81714fd69d41e9cf4fb436d81796fbafb4740e0b
Timestamp: 1696685460 Timestamp [UCT]: 2023-10-07 13:31:00 Age [y:d:h:m:s]: 01:095:14:10:39
Block: 864471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329571 RingCT/type: yes/0
Extra: 01f62e92924b7eeedfa7891a9a81714fd69d41e9cf4fb436d81796fbafb4740e0b021100000003faf35c9c000000000000000000

1 output(s) for total of 0.838781327000 dcy

stealth address amount amount idx
00: 22220beadfe87eb1d9e4094eb4f41be0d6a05716416611f58a9232a0c2131318 0.838781327000 1318985 of 0

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": 864481, "vin": [ { "gen": { "height": 864471 } } ], "vout": [ { "amount": 838781327, "target": { "key": "22220beadfe87eb1d9e4094eb4f41be0d6a05716416611f58a9232a0c2131318" } } ], "extra": [ 1, 246, 46, 146, 146, 75, 126, 238, 223, 167, 137, 26, 154, 129, 113, 79, 214, 157, 65, 233, 207, 79, 180, 54, 216, 23, 150, 251, 175, 180, 116, 14, 11, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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