← previous blocknext block →recent activity
Analyzing
Block #99,263,295
35 transactions · 24 stateful · 2026-08-26 06:58:07 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
0.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,263,295 · 35 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
3w04w05w16w29w110w312w014w415w519w323w625w026w129w233w334w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…0000
0x63e48b…53f2
8 touches
6 conflicts
0x9a555477…19a8
0x754704…b603
8 touches
6 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0004
0x63e48b…53f2
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity