Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d126d943e92eb23f73cc21736112594d72da364662e6ce21ff46f792a7f44e91

Tx prefix hash: bd5f91493200c2cc3b4d1212a4e964c624c4765c43e5aa448f6f1fdbde8a4b04
Tx public key: fa0d9bd3c9e434f61af92861596aced506509d88d91a19ba9edc214d60fcd667
Timestamp: 1718500792 Timestamp [UCT]: 2024-06-16 01:19:52 Age [y:d:h:m:s]: 00:364:05:23:04
Block: 1045143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260222 RingCT/type: yes/0
Extra: 01fa0d9bd3c9e434f61af92861596aced506509d88d91a19ba9edc214d60fcd66702110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02b3c91f1257fc13cb551e85482c80a3ddbf9e2f0e93e7b136856501a96cd194 0.600000000000 1514640 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": 1045153, "vin": [ { "gen": { "height": 1045143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02b3c91f1257fc13cb551e85482c80a3ddbf9e2f0e93e7b136856501a96cd194" } } ], "extra": [ 1, 250, 13, 155, 211, 201, 228, 52, 246, 26, 249, 40, 97, 89, 106, 206, 213, 6, 80, 157, 136, 217, 26, 25, 186, 158, 220, 33, 77, 96, 252, 214, 103, 2, 17, 0, 0, 0, 9, 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