Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f68b114098b770cde9bc2bc6b87d7891c67b2f823a92e45c876269a4e90d6d1b

Tx prefix hash: cd08dab280906816b806b3e37c91edcca263ecce27d4648db22268445914f24e
Tx public key: 9fb61398375c6010670fd94eb38f91514cf5f786657bd1f0d220e201b5fd4a25
Timestamp: 1582408510 Timestamp [UCT]: 2020-02-22 21:55:10 Age [y:d:h:m:s]: 05:076:08:15:51
Block: 70435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1207821 RingCT/type: yes/0
Extra: 019fb61398375c6010670fd94eb38f91514cf5f786657bd1f0d220e201b5fd4a2502110000001c8a2ee0d9000000000000000000

1 output(s) for total of 358.608359437000 dcy

stealth address amount amount idx
00: 26eb1a49879c9c5618d2cd70c654aeecd2bb9cb580d3469c1c52785aa6279744 358.608359437000 130153 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": 70445, "vin": [ { "gen": { "height": 70435 } } ], "vout": [ { "amount": 358608359437, "target": { "key": "26eb1a49879c9c5618d2cd70c654aeecd2bb9cb580d3469c1c52785aa6279744" } } ], "extra": [ 1, 159, 182, 19, 152, 55, 92, 96, 16, 103, 15, 217, 78, 179, 143, 145, 81, 76, 245, 247, 134, 101, 123, 209, 240, 210, 32, 226, 1, 181, 253, 74, 37, 2, 17, 0, 0, 0, 28, 138, 46, 224, 217, 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