Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e20df52b19d4f086a6d556b189577bd607a8c529a4a05c2e56e97d5f6a43da06

Tx prefix hash: 65529b2025114cc901fe9ede0d0bd27064e606e1bab7b8fa1978bd49682f88d7
Tx public key: 9813584640b57bfb33978b04449a7c6e4295851d7b78cb3115ed9bb4c85db891
Timestamp: 1579077290 Timestamp [UCT]: 2020-01-15 08:34:50 Age [y:d:h:m:s]: 04:348:05:32:26
Block: 45919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1138423 RingCT/type: yes/0
Extra: 019813584640b57bfb33978b04449a7c6e4295851d7b78cb3115ed9bb4c85db891021100000005b221b3d1000000000000000000

1 output(s) for total of 432.374052462000 dcy

stealth address amount amount idx
00: bd60ea64fcd7f8d5ecd28278ba5732c44bcfa3f82e570498cb6821d795d2bd0a 432.374052462000 84186 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": 45929, "vin": [ { "gen": { "height": 45919 } } ], "vout": [ { "amount": 432374052462, "target": { "key": "bd60ea64fcd7f8d5ecd28278ba5732c44bcfa3f82e570498cb6821d795d2bd0a" } } ], "extra": [ 1, 152, 19, 88, 70, 64, 181, 123, 251, 51, 151, 139, 4, 68, 154, 124, 110, 66, 149, 133, 29, 123, 120, 203, 49, 21, 237, 155, 180, 200, 93, 184, 145, 2, 17, 0, 0, 0, 5, 178, 33, 179, 209, 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