← previous blocknext block →recent activity
Analyzing
Block #108,467,118
19 transactions · 16 stateful · 2026-09-27 12:37:45 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,467,118 · 19 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
2w05w07w18w211w315w118w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0x0215d8e5…68d5
0x34b655…2a6f
2 touches
0 conflicts
0x1005af85…9f41
0x34b655…2a6f
2 touches
0 conflicts
0x31b513ff…b247
0x34b655…2a6f
2 touches
0 conflicts
0x625c4ed4…16aa
0x34b655…2a6f
2 touches
0 conflicts
0x6542051a…b476
0x34b655…2a6f
2 touches
0 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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity