Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9467aa5ea03efc065ab806160eadc25f685f0ee48c465c66e2f63eea354e3989

Tx prefix hash: 9a3cfd51ac40165b7c5cfecc710a9326560b5ca439a55567f98de0ea81116861
Tx public key: c9c956f0270a2dd4d20e3a3ff834a6ddf87c38fb0130a32dbcc1e13d96cd566c
Timestamp: 1684131929 Timestamp [UCT]: 2023-05-15 06:25:29 Age [y:d:h:m:s]: 01:248:12:55:38
Block: 760449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439074 RingCT/type: yes/0
Extra: 01c9c956f0270a2dd4d20e3a3ff834a6ddf87c38fb0130a32dbcc1e13d96cd566c02110000000133af99f4000000000000000000

1 output(s) for total of 1.854884933000 dcy

stealth address amount amount idx
00: 316f9d5af32b4bc773dee01f78db37af9243556bb3b2b265c87da40b6f382585 1.854884933000 1209052 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": 760459, "vin": [ { "gen": { "height": 760449 } } ], "vout": [ { "amount": 1854884933, "target": { "key": "316f9d5af32b4bc773dee01f78db37af9243556bb3b2b265c87da40b6f382585" } } ], "extra": [ 1, 201, 201, 86, 240, 39, 10, 45, 212, 210, 14, 58, 63, 248, 52, 166, 221, 248, 124, 56, 251, 1, 48, 163, 45, 188, 193, 225, 61, 150, 205, 86, 108, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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