← previous blocknext block →recent activity
Analyzing
Block #99,189,650
25 transactions · 19 stateful · 2026-08-26 00:47:30 UTC
Parallelism
76/100
Blocked
42%
Avg conflicts / tx
0.56
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,189,650 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w07w18w09w010w011w112w214w017w320w421w122w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x382434ca…96b5
0x34b655…2a6f
6 touches
3 conflicts
0x38bcfe5f…6c71
0x34b655…2a6f
6 touches
3 conflicts
0x25180879…8191
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x9e5939a7…9ecc
0x34b655…2a6f
6 touches
3 conflicts
0xee842626…886d
0x34b655…2a6f
6 touches
3 conflicts
0x4bb4d9a2…62bc
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
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
3 conflicts on slot 0x382434ca57…4d96b5
Audit this contract →
← previous block·next block →recent activity