← previous blocknext block →recent activity
Analyzing
Block #108,533,913
21 transactions · 16 stateful · 2026-09-27 18:14:00 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
0.76
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,533,913 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w29w010w111w212w213w317w018w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3e67fe3…e754
0x37db7f…ec7b
8 touches
6 conflicts
0x5164ab0e…01e1
0xc8689a…ee79
8 touches
6 conflicts
0x085df2c1…305a
0x34b655…2a6f
8 touches
6 conflicts
0x15698ac9…2a46
0x34b655…2a6f
8 touches
6 conflicts
0x366a19b0…f065
0x34b655…2a6f
8 touches
6 conflicts
0x3952b40f…4c8c
0x34b655…2a6f
8 touches
6 conflicts
0x5086c64a…28ba
0x34b655…2a6f
8 touches
6 conflicts
0x68292fe7…d918
0x34b655…2a6f
8 touches
6 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: 0x37db7fbf…3eec7b
6 conflicts on slot 0xe3e67fe32d…a9e754
Audit this contract →
← previous block·next block →recent activity