← previous blocknext block →recent activity
Analyzing
Block #99,188,913
16 transactions · 16 stateful · 2026-08-26 00:43:48 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,188,913 · 16 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
1w04w16w07w08w09w110w111w012w215w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa93f84a…5a0b
0x34b655…2a6f
6 touches
3 conflicts
0xaf498679…7732
0x34b655…2a6f
6 touches
3 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
6 touches
3 conflicts
0xd97b0449…00a0
0x34b655…2a6f
6 touches
3 conflicts
0x107b89e4…470d
0x34b655…2a6f
6 touches
3 conflicts
0xec27dc24…8c35
0x34b655…2a6f
6 touches
3 conflicts
0xf04fd2fd…bc43
0x34b655…2a6f
6 touches
3 conflicts
0x00f245ce…1e10
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
3 conflicts on slot 0xaa93f84a8d…435a0b
Audit this contract →
← previous block·next block →recent activity