← previous blocknext block →recent activity
Analyzing
Block #108,477,001
20 transactions · 18 stateful · 2026-09-27 13:27:30 UTC
Parallelism
70/100
Blocked
56%
Avg conflicts / tx
1.15
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,477,001 · 20 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
4w05w17w08w19w210w211w312w413w514w016w017w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26b816a2…89a5
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x1a1c67e2…7f7d
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xcd0e79e1…4c56
0x34b655…2a6f
6 touches
3 conflicts
0x9903f679…b85c
0x34b655…2a6f
6 touches
3 conflicts
0xdfe93359…9ea7
0x34b655…2a6f
6 touches
3 conflicts
0x481db2dd…cc35
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 0x26b816a256…ea89a5
Audit this contract →
← previous block·next block →recent activity