Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 746979565695ce8967dc7bccd091c64e9c2993d1d6c0c43ad29d3350611b82ec

Tx prefix hash: 0401ece3659e6fe60d1020b0b76ef852faf659fef9efa30ccbd07a339494375f
Tx public key: 8b5ac64c34cefdb39ff943b5a01552234c531f4f2e562b32ae5ddbd2464e1617
Timestamp: 1727975707 Timestamp [UCT]: 2024-10-03 17:15:07 Age [y:d:h:m:s]: 00:209:12:10:33
Block: 1123683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149533 RingCT/type: yes/0
Extra: 018b5ac64c34cefdb39ff943b5a01552234c531f4f2e562b32ae5ddbd2464e1617021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e74a2fa0ab817d70fb571baaf774f390d2184ab686426c6f61fec6f2a1eea0a7 0.600000000000 1606218 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": 1123693, "vin": [ { "gen": { "height": 1123683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e74a2fa0ab817d70fb571baaf774f390d2184ab686426c6f61fec6f2a1eea0a7" } } ], "extra": [ 1, 139, 90, 198, 76, 52, 206, 253, 179, 159, 249, 67, 181, 160, 21, 82, 35, 76, 83, 31, 79, 46, 86, 43, 50, 174, 93, 219, 210, 70, 78, 22, 23, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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