Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba8a659068ea58b3fc44998b5f84caf0478425951fb2a9a6ceb6c86feff9722a

Tx prefix hash: 09f9b1543493a6e7fda65b8b5f49e10dc0bac8a4e9956dce7b1fe775600fde54
Tx public key: 4d57f8047f74a3871918d04360007489ef4ff0644b21321a7cc4dc3280657e10
Timestamp: 1696705932 Timestamp [UCT]: 2023-10-07 19:12:12 Age [y:d:h:m:s]: 01:202:13:31:41
Block: 864639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405826 RingCT/type: yes/0
Extra: 014d57f8047f74a3871918d04360007489ef4ff0644b21321a7cc4dc3280657e10021100000002faf35c9c000000000000000000

1 output(s) for total of 0.837706913000 dcy

stealth address amount amount idx
00: e6f812abdf98d87bcdd80cb515f402381b94cf58cb1a6d283c573c7024e5ab6c 0.837706913000 1319159 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": 864649, "vin": [ { "gen": { "height": 864639 } } ], "vout": [ { "amount": 837706913, "target": { "key": "e6f812abdf98d87bcdd80cb515f402381b94cf58cb1a6d283c573c7024e5ab6c" } } ], "extra": [ 1, 77, 87, 248, 4, 127, 116, 163, 135, 25, 24, 208, 67, 96, 0, 116, 137, 239, 79, 240, 100, 75, 33, 50, 26, 124, 196, 220, 50, 128, 101, 126, 16, 2, 17, 0, 0, 0, 2, 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