← previous blocknext block →recent activity
Analyzing
Block #108,501,425
23 transactions · 20 stateful · 2026-09-27 15:30:28 UTC
Parallelism
78/100
Blocked
55%
Avg conflicts / tx
0.96
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,501,425 · 23 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
1w02w03w19w110w211w112w213w014w115w216w217w318w420w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9ea37a1…bef6
0x34b655…2a6f
8 touches
6 conflicts
0xd1448207…452d
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x19dcf812…44d9
0x34b655…2a6f
6 touches
3 conflicts
0x3fcf90a0…38a6
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x6302c76f…a5d2
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xb9ea37a1ee…dfbef6
Audit this contract →
← previous block·next block →recent activity