Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e69723954b8e13dbebbcd12e15cbaa14436c711d470b38f7d4f8d17c23d41fe0

Tx prefix hash: 89142f1ca21f9ef17c27c731003302b826564da666deab8524499d9c0406dd65
Tx public key: 30d8a9c7e110f5619694a63b726b383b4b69c4e65184f841465a9c9024fa99de
Timestamp: 1704658621 Timestamp [UCT]: 2024-01-07 20:17:01 Age [y:d:h:m:s]: 01:130:13:12:17
Block: 930344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354456 RingCT/type: yes/0
Extra: 0130d8a9c7e110f5619694a63b726b383b4b69c4e65184f841465a9c9024fa99de02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 292841f0ade17e43cb2d501a031dc7e5b45baf12dd80141f3846f485fce1e0d2 0.600000000000 1388226 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": 930354, "vin": [ { "gen": { "height": 930344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "292841f0ade17e43cb2d501a031dc7e5b45baf12dd80141f3846f485fce1e0d2" } } ], "extra": [ 1, 48, 216, 169, 199, 225, 16, 245, 97, 150, 148, 166, 59, 114, 107, 56, 59, 75, 105, 196, 230, 81, 132, 248, 65, 70, 90, 156, 144, 36, 250, 153, 222, 2, 17, 0, 0, 0, 2, 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