← previous blocknext block →recent activity
Analyzing
Block #99,133,286
17 transactions · 16 stateful · 2026-08-25 20:03:57 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,133,286 · 17 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
1w05w09w010w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdeaa385f…6b8b
0x34b655…2a6f
4 touches
1 conflict
0xea3ad79b…044f
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x0d816e2e…67a1
0x34b655…2a6f
2 touches
0 conflicts
0x62910921…3016
0x34b655…2a6f
2 touches
0 conflicts
0x807bf45f…5016
0x34b655…2a6f
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 0xdeaa385f73…d36b8b
Audit this contract →
← previous block·next block →recent activity