Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 907bdd82f3e5db9a703ec81a217fa511685f5623b49172a8f73ae280be94fbc6

Tx prefix hash: 3292aa24f90e97a842afd5adda8f9434f1a4bce2ad2d0d60cebec352d748e116
Tx public key: adde67b9e46eb1c5ac3ff21c318c41b34e7133c28a3bd4a50f46715394d80f5d
Timestamp: 1729582775 Timestamp [UCT]: 2024-10-22 07:39:35 Age [y:d:h:m:s]: 00:000:03:44:19
Block: 1136965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117 RingCT/type: yes/0
Extra: 01adde67b9e46eb1c5ac3ff21c318c41b34e7133c28a3bd4a50f46715394d80f5d021100000001aa787773000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cf82287e898823422b96779e06c8f0a9dcd422d69a20f2d9cce3cbcbf999eea 0.600000000000 1620368 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": 1136975, "vin": [ { "gen": { "height": 1136965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cf82287e898823422b96779e06c8f0a9dcd422d69a20f2d9cce3cbcbf999eea" } } ], "extra": [ 1, 173, 222, 103, 185, 228, 110, 177, 197, 172, 63, 242, 28, 49, 140, 65, 179, 78, 113, 51, 194, 138, 59, 212, 165, 15, 70, 113, 83, 148, 216, 15, 93, 2, 17, 0, 0, 0, 1, 170, 120, 119, 115, 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