Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 437e9aff61d1a9cc2e55518ec294aaa4ffd86298d7331fa5dc610baffc2c5ce2

Tx prefix hash: ae4f261c7ed52c7d60c4ef1e8bb6ee403c733beed4f6942c7c7a38f371118a55
Tx public key: 35168736106fdbde0e5d715b0103a5d2ae544741d6e45584ec3c53a341d774c5
Timestamp: 1636989039 Timestamp [UCT]: 2021-11-15 15:10:39 Age [y:d:h:m:s]: 03:084:01:28:22
Block: 374887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 838596 RingCT/type: yes/0
Extra: 0135168736106fdbde0e5d715b0103a5d2ae544741d6e45584ec3c53a341d774c5021100000004a272b9cb000000000000000000

1 output(s) for total of 35.143428928000 dcy

stealth address amount amount idx
00: 5e6b548f63fbd69789ad3a4508f79c34332a34b8f8f6806284ac4d852e2b96c2 35.143428928000 758707 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": 374897, "vin": [ { "gen": { "height": 374887 } } ], "vout": [ { "amount": 35143428928, "target": { "key": "5e6b548f63fbd69789ad3a4508f79c34332a34b8f8f6806284ac4d852e2b96c2" } } ], "extra": [ 1, 53, 22, 135, 54, 16, 111, 219, 222, 14, 93, 113, 91, 1, 3, 165, 210, 174, 84, 71, 65, 214, 228, 85, 132, 236, 60, 83, 163, 65, 215, 116, 197, 2, 17, 0, 0, 0, 4, 162, 114, 185, 203, 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