← previous blocknext block →recent activity
Analyzing
Block #100,986,313
19 transactions · 19 stateful · 2026-09-01 07:47:21 UTC
Parallelism
74/100
Blocked
37%
Avg conflicts / tx
0.84
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,986,313 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w09w110w212w313w216w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x772cc8de…65e8
0x34b655…2a6f
10 touches
10 conflicts
0xf788c790…e66f
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x3ee8b564…4c49
0x34b655…2a6f
6 touches
3 conflicts
0x50773f07…b37c
0x34b655…2a6f
4 touches
1 conflict
0x524f0872…0d12
0x34b655…2a6f
4 touches
1 conflict
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x0dd3d3cd…7281
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
10 conflicts on slot 0x772cc8de6d…8a65e8
Audit this contract →
← previous block·next block →recent activity