Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09d5ac9544b6df2f78fcc1eb3a87140037147d6ffa0c40e9659a1b3531446f77

Tx prefix hash: dbc893259f664322add968ac3ffa0994eccb7d659494d9eb0a5d4ce11426beba
Tx public key: 2b2511ad3e738ff11ad9137f67b1108ac1d10d5767dccb4c75476e8cbddd0e5b
Timestamp: 1698418532 Timestamp [UCT]: 2023-10-27 14:55:32 Age [y:d:h:m:s]: 01:170:06:59:04
Block: 878848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382705 RingCT/type: yes/0
Extra: 012b2511ad3e738ff11ad9137f67b1108ac1d10d5767dccb4c75476e8cbddd0e5b0211000000024b8f5122000000000000000000

1 output(s) for total of 0.751643253000 dcy

stealth address amount amount idx
00: cd4f91c8283e65f6046cdd039f50e2c18ebfd7492cf84a87cdeb20479ada031d 0.751643253000 1334338 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": 878858, "vin": [ { "gen": { "height": 878848 } } ], "vout": [ { "amount": 751643253, "target": { "key": "cd4f91c8283e65f6046cdd039f50e2c18ebfd7492cf84a87cdeb20479ada031d" } } ], "extra": [ 1, 43, 37, 17, 173, 62, 115, 143, 241, 26, 217, 19, 127, 103, 177, 16, 138, 193, 209, 13, 87, 103, 220, 203, 76, 117, 71, 110, 140, 189, 221, 14, 91, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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