Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5f1c95ee15614bd28c2bccf6c90324d13d13554e1605c29b801448fe8703e93

Tx prefix hash: b7219334c593418256c989853f1c3d92dd3fbfa568ce7005082cba7f900f1d03
Tx public key: f68b5fe5378c243b6367e1e743caddcb16e095fad7e30a08b189f0a757e11802
Timestamp: 1712341527 Timestamp [UCT]: 2024-04-05 18:25:27 Age [y:d:h:m:s]: 01:038:12:16:20
Block: 994030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288543 RingCT/type: yes/0
Extra: 01f68b5fe5378c243b6367e1e743caddcb16e095fad7e30a08b189f0a757e1180202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d908d8758a9adda5c99e58d0f95b5bc9db02e0e143b9a17cc36a07174dfb7fde 0.600000000000 1454426 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": 994040, "vin": [ { "gen": { "height": 994030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d908d8758a9adda5c99e58d0f95b5bc9db02e0e143b9a17cc36a07174dfb7fde" } } ], "extra": [ 1, 246, 139, 95, 229, 55, 140, 36, 59, 99, 103, 225, 231, 67, 202, 221, 203, 22, 224, 149, 250, 215, 227, 10, 8, 177, 137, 240, 167, 87, 225, 24, 2, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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