Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a404c9ecd0be33d15532ecc1196ce07805bb9fdda2e332a2973d291336fadf6e

Tx prefix hash: 47676b843f8668f928204cd3c7f563f0ee05ca29d135411b0dfb09220be8af65
Tx public key: e20021794d5d83093c60346cbc4b2426f49a1be65c22c4d9b3850da27c0bb449
Timestamp: 1707160195 Timestamp [UCT]: 2024-02-05 19:09:55 Age [y:d:h:m:s]: 00:358:10:38:27
Block: 951099 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256348 RingCT/type: yes/0
Extra: 01e20021794d5d83093c60346cbc4b2426f49a1be65c22c4d9b3850da27c0bb44902110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 648dfe9fc4a52e640c054c83a87dc0523d8cbd3a56673597899b6bb7b36ea1d3 0.600000000000 1409821 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": 951109, "vin": [ { "gen": { "height": 951099 } } ], "vout": [ { "amount": 600000000, "target": { "key": "648dfe9fc4a52e640c054c83a87dc0523d8cbd3a56673597899b6bb7b36ea1d3" } } ], "extra": [ 1, 226, 0, 33, 121, 77, 93, 131, 9, 60, 96, 52, 108, 188, 75, 36, 38, 244, 154, 27, 230, 92, 34, 196, 217, 179, 133, 13, 162, 124, 11, 180, 73, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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