Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1e4c6579ae861354475fa6d82bc9033f8acca72a689d1668c21c7d2c4f4fd70

Tx prefix hash: 9a47120442b19e2dcb72010623eca84e1eaa49ef695654104d543f61907761ed
Tx public key: 1131c1669e922fe6e323d4448fab8b9b98a84c7c5d46085e84c1500c2e4013ef
Timestamp: 1673930369 Timestamp [UCT]: 2023-01-17 04:39:29 Age [y:d:h:m:s]: 02:093:06:24:03
Block: 676468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 588340 RingCT/type: yes/0
Extra: 011131c1669e922fe6e323d4448fab8b9b98a84c7c5d46085e84c1500c2e4013ef0211000000018b7b6602000000000000000000

1 output(s) for total of 3.520307886000 dcy

stealth address amount amount idx
00: 003824b7d504ecd8c26a917fdc139c2034621181791213ce3327f71afe1d83eb 3.520307886000 1118185 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": 676478, "vin": [ { "gen": { "height": 676468 } } ], "vout": [ { "amount": 3520307886, "target": { "key": "003824b7d504ecd8c26a917fdc139c2034621181791213ce3327f71afe1d83eb" } } ], "extra": [ 1, 17, 49, 193, 102, 158, 146, 47, 230, 227, 35, 212, 68, 143, 171, 139, 155, 152, 168, 76, 124, 93, 70, 8, 94, 132, 193, 80, 12, 46, 64, 19, 239, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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