Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f0de6165dc2311fcdba4bdd3a92615a6e4a7db79bfa8a6d0517380666675345

Tx prefix hash: 416d7496a14dfcb3e2b1b7fbfcfeb74976fca31ae20f8a215170fb0c616e2f7c
Tx public key: f807177f314d08e887a541cd94f9a989e9fed0ef28a3af80f451a0c1305b4b8f
Timestamp: 1690048672 Timestamp [UCT]: 2023-07-22 17:57:52 Age [y:d:h:m:s]: 01:183:13:31:28
Block: 809508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392479 RingCT/type: yes/0
Extra: 01f807177f314d08e887a541cd94f9a989e9fed0ef28a3af80f451a0c1305b4b8f021100000004e6d27f9c000000000000000000

1 output(s) for total of 1.275745571000 dcy

stealth address amount amount idx
00: 803d0433a6b35329bca65025d3e25e383235e2ab1706a3ac8c65d597199de3d1 1.275745571000 1261115 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": 809518, "vin": [ { "gen": { "height": 809508 } } ], "vout": [ { "amount": 1275745571, "target": { "key": "803d0433a6b35329bca65025d3e25e383235e2ab1706a3ac8c65d597199de3d1" } } ], "extra": [ 1, 248, 7, 23, 127, 49, 77, 8, 232, 135, 165, 65, 205, 148, 249, 169, 137, 233, 254, 208, 239, 40, 163, 175, 128, 244, 81, 160, 193, 48, 91, 75, 143, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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