Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b43ef6d14317a1e2993f89eff9b68206e67d3960252b76a1a4a2379a9ec184e0

Tx prefix hash: 42f2b203013f62f51b60d2d8019cf7b986d0fef1d7b2d55c312d516629f53868
Tx public key: 28a519447457aa47897a02f9deef141dfd211e5f78e6e0985a10559d8269ba72
Timestamp: 1714353501 Timestamp [UCT]: 2024-04-29 01:18:21 Age [y:d:h:m:s]: 00:209:09:39:33
Block: 1010734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149904 RingCT/type: yes/0
Extra: 0128a519447457aa47897a02f9deef141dfd211e5f78e6e0985a10559d8269ba7202110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b33782d91f9be920d32ca5e959030ac19f77f0386a618b6644989404b4cd3a9 0.600000000000 1472772 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": 1010744, "vin": [ { "gen": { "height": 1010734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b33782d91f9be920d32ca5e959030ac19f77f0386a618b6644989404b4cd3a9" } } ], "extra": [ 1, 40, 165, 25, 68, 116, 87, 170, 71, 137, 122, 2, 249, 222, 239, 20, 29, 253, 33, 30, 95, 120, 230, 224, 152, 90, 16, 85, 157, 130, 105, 186, 114, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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