← previous blocknext block →recent activity
Analyzing
Block #108,433,308
11 transactions · 11 stateful · 2026-09-27 09:47:34 UTC
Parallelism
55/100
Blocked
55%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,433,308 · 11 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
3w04w15w26w17w38w49w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18e60108…c16d
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x966b7ff8…268d
0x34b655…2a6f
6 touches
3 conflicts
0xf3b3a6e9…8cd2
0x34b655…2a6f
4 touches
1 conflict
0x8cd0c8dc…33f5
0x34b655…2a6f
4 touches
1 conflict
0x977d1a96…7256
0x34b655…2a6f
4 touches
1 conflict
0x9b419d78…018b
0x34b655…2a6f
4 touches
1 conflict
0xbe5136a4…7708
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 0x18e6010847…2fc16d
Audit this contract →
← previous block·next block →recent activity