← previous blocknext block →recent activity
Analyzing
Block #99,870,402
21 transactions · 20 stateful · 2026-08-28 10:07:23 UTC
Parallelism
86/100
Blocked
35%
Avg conflicts / tx
0.48
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,870,402 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w08w19w212w013w114w116w017w118w220w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53ca1284…cb2c
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xe7ad475a…0e41
0x34b655…2a6f
6 touches
3 conflicts
0xd34a300b…0b06
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x04f4016d…10e3
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
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 0x53ca128412…cacb2c
Audit this contract →
← previous block·next block →recent activity