← previous blocknext block →recent activity
Analyzing
Block #99,134,570
9 transactions · 9 stateful · 2026-08-25 20:10:25 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,134,570 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x605e358e…dc99
0x34b655…2a6f
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0xca09298a…0bc9
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x2b46c0…1669
2 touches
0 conflicts
0x45f562b2…9294
0x2b46c0…1669
2 touches
0 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
1 conflict on slot 0x605e358e22…48dc99
Audit this contract →
← previous block·next block →recent activity