Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33a26e6ae773270c72bde744d7cc3c279e0d5578ea12c0c5d7c41f5674a5bfe3

Tx prefix hash: 781cfc9bebadb0b5f52dd44a77553aa8ec7752158f8e402cb7acc9f7feececbd
Tx public key: 28e8341068596f89a45b6c871e735146d5012e2fa98f11ac4e4c4343218fa621
Timestamp: 1658471680 Timestamp [UCT]: 2022-07-22 06:34:40 Age [y:d:h:m:s]: 02:159:06:47:57
Block: 549090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 635226 RingCT/type: yes/0
Extra: 0128e8341068596f89a45b6c871e735146d5012e2fa98f11ac4e4c4343218fa621021100000002a8c141c5000000000000000000

1 output(s) for total of 9.303299996000 dcy

stealth address amount amount idx
00: ae9f508abeb2a927e8e9f90be54bff8afd3689702a7b43847af86d50f7382949 9.303299996000 980415 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": 549100, "vin": [ { "gen": { "height": 549090 } } ], "vout": [ { "amount": 9303299996, "target": { "key": "ae9f508abeb2a927e8e9f90be54bff8afd3689702a7b43847af86d50f7382949" } } ], "extra": [ 1, 40, 232, 52, 16, 104, 89, 111, 137, 164, 91, 108, 135, 30, 115, 81, 70, 213, 1, 46, 47, 169, 143, 17, 172, 78, 76, 67, 67, 33, 143, 166, 33, 2, 17, 0, 0, 0, 2, 168, 193, 65, 197, 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