Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eedcd332c1ce8ea0e9d44bd501d27b270e89a747fe74d7eb81ca6995188f30a8

Tx prefix hash: cdbee169f22df1bd980dc21dea088615a29050057a48f852c6b2bf18b51a7912
Tx public key: 7bb1fbb3c0644fd02519a323583f4b38911824104f564a7005a74b0795ae2a6f
Timestamp: 1694335731 Timestamp [UCT]: 2023-09-10 08:48:51 Age [y:d:h:m:s]: 01:106:03:56:36
Block: 844969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337199 RingCT/type: yes/0
Extra: 017bb1fbb3c0644fd02519a323583f4b38911824104f564a7005a74b0795ae2a6f0211000000074b8f5122000000000000000000

1 output(s) for total of 0.973345451000 dcy

stealth address amount amount idx
00: 7eccda0db7644ca1a05f92945ade12e544d36b15c9d8691320180fd3dbb23268 0.973345451000 1298313 of 0

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": 844979, "vin": [ { "gen": { "height": 844969 } } ], "vout": [ { "amount": 973345451, "target": { "key": "7eccda0db7644ca1a05f92945ade12e544d36b15c9d8691320180fd3dbb23268" } } ], "extra": [ 1, 123, 177, 251, 179, 192, 100, 79, 208, 37, 25, 163, 35, 88, 63, 75, 56, 145, 24, 36, 16, 79, 86, 74, 112, 5, 167, 75, 7, 149, 174, 42, 111, 2, 17, 0, 0, 0, 7, 75, 143, 81, 34, 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