Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38806c13abd2dc94b2f77dd81c071529dff1a3ff6d8bb15740161c32a71bcdeb

Tx prefix hash: 19ea7664c164fd6a47794f7c2d0a534c8ad35b6cc1fa88c5b856eb74babde76e
Tx public key: e5eff5fedd06ccaf22fd5c6e842cb95418c8321023eb26f4eb54189a2aaea972
Timestamp: 1722505592 Timestamp [UCT]: 2024-08-01 09:46:32 Age [y:d:h:m:s]: 00:160:19:20:24
Block: 1078317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115054 RingCT/type: yes/0
Extra: 01e5eff5fedd06ccaf22fd5c6e842cb95418c8321023eb26f4eb54189a2aaea97202110000000fe914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e2c4e2859c64fc5c70b8f4ae66ef1634408bde4f4f38f94458867888bfff427 0.600000000000 1550894 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": 1078327, "vin": [ { "gen": { "height": 1078317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e2c4e2859c64fc5c70b8f4ae66ef1634408bde4f4f38f94458867888bfff427" } } ], "extra": [ 1, 229, 239, 245, 254, 221, 6, 204, 175, 34, 253, 92, 110, 132, 44, 185, 84, 24, 200, 50, 16, 35, 235, 38, 244, 235, 84, 24, 154, 42, 174, 169, 114, 2, 17, 0, 0, 0, 15, 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