Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a32e042374e82c796c457e4bcbc1b710098e39902f4692d41989f1d2aad3791

Tx prefix hash: ca3ff03fd35f8ed1a1ef72353b133c39257bc5f309ec089cbf9d29b6792642c3
Tx public key: e875204494487c35290da69d1ce62500a165f467e4a6b734d5cdcac7ab489a7f
Timestamp: 1695513469 Timestamp [UCT]: 2023-09-23 23:57:49 Age [y:d:h:m:s]: 02:052:15:06:29
Block: 854747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 557274 RingCT/type: yes/0
Extra: 01e875204494487c35290da69d1ce62500a165f467e4a6b734d5cdcac7ab489a7f021100000005faf35c9c000000000000000000

1 output(s) for total of 0.903375725000 dcy

stealth address amount amount idx
00: f4d957fd80b8e85d580c6be93da3eb766cb12e943767f2e03ce24fbaeb42b773 0.903375725000 1308733 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": 854757, "vin": [ { "gen": { "height": 854747 } } ], "vout": [ { "amount": 903375725, "target": { "key": "f4d957fd80b8e85d580c6be93da3eb766cb12e943767f2e03ce24fbaeb42b773" } } ], "extra": [ 1, 232, 117, 32, 68, 148, 72, 124, 53, 41, 13, 166, 157, 28, 230, 37, 0, 161, 101, 244, 103, 228, 166, 183, 52, 213, 205, 202, 199, 171, 72, 154, 127, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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