← previous blocknext block →recent activity

Analyzing

Block #93,369,428

22 transactions · 21 stateful · 2026-08-05 14:21:08 UTC

Parallelism

68/100

Blocked

52%

Avg conflicts / tx

1.41

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #93,369,428  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0x808129fc…f97d

0x34b655…2a6f

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x34a1ee7e…fb20

0x34b655…2a6f

8 touches
6 conflicts

0x07d94be1…7fa8

0x34b655…2a6f

6 touches
3 conflicts

0x39f2fdd2…9204

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x50c730d7…8540

0x34b655…2a6f

6 touches
3 conflicts

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: Perpl

6 conflicts on slot 0xea02471df2…601542

← previous block·next block →recent activity