← previous blocknext block →recent activity
Analyzing
Block #108,344,332
21 transactions · 15 stateful · 2026-09-27 02:19:48 UTC
Parallelism
86/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,344,332 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w16w07w111w113w114w015w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6de158b…6fdd
0x34b655…2a6f
6 touches
3 conflicts
0x3da6ec2b…b836
0x34b655…2a6f
6 touches
3 conflicts
0x51087f5a…61f7
0x34b655…2a6f
4 touches
1 conflict
0x70986451…c6bd
0x34b655…2a6f
4 touches
1 conflict
0x9670dc06…c488
0x34b655…2a6f
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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 0xb6de158b50…9d6fdd
Audit this contract →
← previous block·next block →recent activity