Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2de6e68f330b5e7afcb4dd0b86135ef0c3021dcbc20f26115899f874ba23dc45

Tx prefix hash: 907116e1861ae70707d9f700f76c62efccee74e4eca4e518310de33169c466d9
Tx public key: 864ea7650cee23d8518e1663f05a4afac1e8b8965399bc8c42be04a81f9b77fb
Timestamp: 1724319920 Timestamp [UCT]: 2024-08-22 09:45:20 Age [y:d:h:m:s]: 00:186:13:32:33
Block: 1093386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133154 RingCT/type: yes/0
Extra: 01864ea7650cee23d8518e1663f05a4afac1e8b8965399bc8c42be04a81f9b77fb021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5ca9e20b743a4004b92d710297c636d03478b6a6f2ad37cb5746215c96b0105 0.600000000000 1568319 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": 1093396, "vin": [ { "gen": { "height": 1093386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5ca9e20b743a4004b92d710297c636d03478b6a6f2ad37cb5746215c96b0105" } } ], "extra": [ 1, 134, 78, 167, 101, 12, 238, 35, 216, 81, 142, 22, 99, 240, 90, 74, 250, 193, 232, 184, 150, 83, 153, 188, 140, 66, 190, 4, 168, 31, 155, 119, 251, 2, 17, 0, 0, 0, 7, 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