Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d76d5cc0f854bc5f6c1c894e972e060ff5e00445657dba2636eb282178e1ea68

Tx prefix hash: e6dabf1a5e332985938a1568f1df8d3cf6877d2e79547ebdbb96149c00fa1662
Tx public key: 418bf21593ae7ae257a7cd77f2a8f48942411a52ece6f3bba2df5902eaeb34b6
Timestamp: 1580767921 Timestamp [UCT]: 2020-02-03 22:12:01 Age [y:d:h:m:s]: 04:289:05:18:14
Block: 57935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1098186 RingCT/type: yes/0
Extra: 01418bf21593ae7ae257a7cd77f2a8f48942411a52ece6f3bba2df5902eaeb34b60211000000084ac5aa02000000000000000000

1 output(s) for total of 394.491923629000 dcy

stealth address amount amount idx
00: 0a757d1c27bc8a52924a197a14f4cc374c9b7c9e81314048edd81bf4d155f08f 394.491923629000 107146 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": 57945, "vin": [ { "gen": { "height": 57935 } } ], "vout": [ { "amount": 394491923629, "target": { "key": "0a757d1c27bc8a52924a197a14f4cc374c9b7c9e81314048edd81bf4d155f08f" } } ], "extra": [ 1, 65, 139, 242, 21, 147, 174, 122, 226, 87, 167, 205, 119, 242, 168, 244, 137, 66, 65, 26, 82, 236, 230, 243, 187, 162, 223, 89, 2, 234, 235, 52, 182, 2, 17, 0, 0, 0, 8, 74, 197, 170, 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