Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a28e143aca557d92ddc9e99f3d267f6f7a1940c273a1bd2fbc336392f5a5b98e

Tx prefix hash: 7b61caf759ed7889067415ecd286d2f18730522e3c9d0baa2f47fdc9a87afec6
Tx public key: 4ae8add148926868558315fdc0f449b9b386b97d1f9f45956954e2b93f971d87
Timestamp: 1579273838 Timestamp [UCT]: 2020-01-17 15:10:38 Age [y:d:h:m:s]: 04:260:06:11:38
Block: 47783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1075305 RingCT/type: yes/0
Extra: 014ae8add148926868558315fdc0f449b9b386b97d1f9f45956954e2b93f971d8702110000000b391a8d0e000000000000000000

1 output(s) for total of 426.261316150000 dcy

stealth address amount amount idx
00: 6c9f89f85a4330ee4662987ba96b20f9113a35b4a8bcafa47b950bdea8534f13 426.261316150000 88214 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": 47793, "vin": [ { "gen": { "height": 47783 } } ], "vout": [ { "amount": 426261316150, "target": { "key": "6c9f89f85a4330ee4662987ba96b20f9113a35b4a8bcafa47b950bdea8534f13" } } ], "extra": [ 1, 74, 232, 173, 209, 72, 146, 104, 104, 85, 131, 21, 253, 192, 244, 73, 185, 179, 134, 185, 125, 31, 159, 69, 149, 105, 84, 226, 185, 63, 151, 29, 135, 2, 17, 0, 0, 0, 11, 57, 26, 141, 14, 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