← previous blocknext block →recent activity
Analyzing
Block #108,401,916
31 transactions · 28 stateful · 2026-09-27 07:09:34 UTC
Parallelism
81/100
Blocked
54%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,401,916 · 31 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w17w28w011w112w213w314w417w520w522w223w328w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x229d2b7e…abdf
0x34b655…2a6f
10 touches
10 conflicts
0x23c8c8dd…7a42
0x34b655…2a6f
10 touches
10 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x6d5d1fb5…86a7
0x34b655…2a6f
8 touches
6 conflicts
0x7006165a…df17
0x34b655…2a6f
8 touches
6 conflicts
0x9daafdf9…bb53
0x34b655…2a6f
8 touches
6 conflicts
0xa9371684…df38
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: Perpl
10 conflicts on slot 0x229d2b7eeb…93abdf
Audit this contract →
← previous block·next block →recent activity