← previous blocknext block →recent activity
Analyzing
Block #108,539,332
18 transactions · 16 stateful · 2026-09-27 18:41:16 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.39
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,539,332 · 18 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
3w04w15w29w010w112w013w115w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x25b1c19a…6d24
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9c4
0x508254…98bd
4 touches
1 conflict
0xb5172086…881d
0x508254…98bd
4 touches
1 conflict
0xe1c4d8e8…ffa8
0x508254…98bd
4 touches
1 conflict
0x4073f47e…39e6
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity