Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eef1ca2ddd65511365e0afd86c18b1fae0c6dc44e4f8ee45c6549dce36e2467e

Tx prefix hash: 067aa271306f5ae0bbc9b77d8d9be8fecc96b8eefd94f945b8075efdc184cb9a
Tx public key: fe007fadecd9d955c517a15030cbc8075ddbee34ba68f76e228cf1a9f9a7c5f3
Timestamp: 1725474997 Timestamp [UCT]: 2024-09-04 18:36:37 Age [y:d:h:m:s]: 00:080:03:27:31
Block: 1102942 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57308 RingCT/type: yes/0
Extra: 01fe007fadecd9d955c517a15030cbc8075ddbee34ba68f76e228cf1a9f9a7c5f3021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e20fa7f65c36205d1d291c76212be4f6b37f746b26b3ff0f59e8fc7bf335ef0 0.600000000000 1579583 of 15

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": 1102952, "vin": [ { "gen": { "height": 1102942 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e20fa7f65c36205d1d291c76212be4f6b37f746b26b3ff0f59e8fc7bf335ef0" } } ], "extra": [ 1, 254, 0, 127, 173, 236, 217, 217, 85, 197, 23, 161, 80, 48, 203, 200, 7, 93, 219, 238, 52, 186, 104, 247, 110, 34, 140, 241, 169, 249, 167, 197, 243, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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