← previous blocknext block →recent activity
Analyzing
Block #99,195,893
20 transactions · 18 stateful · 2026-08-26 01:18:55 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
1.45
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,195,893 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w17w29w310w415w516w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xb1856468…e84f
0x34b655…2a6f
10 touches
10 conflicts
0x3266bf53…8872
0x34b655…2a6f
8 touches
6 conflicts
0xfb4fd6ce…262e
0x34b655…2a6f
6 touches
3 conflicts
0x4a876a12…694e
0x34b655…2a6f
6 touches
3 conflicts
0x5984f63c…7fca
0x34b655…2a6f
6 touches
3 conflicts
0x6c60fbcf…8744
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity