← previous blocknext block →recent activity
Analyzing
Block #108,657,975
20 transactions · 19 stateful · 2026-09-28 04:38:50 UTC
Parallelism
75/100
Blocked
37%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,657,975 · 20 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
1w02w19w011w012w113w214w215w316w418w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x25957369…c648
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x900e0d7a…6f85
0x34b655…2a6f
6 touches
3 conflicts
0x263f13d4…6815
0x34b655…2a6f
4 touches
1 conflict
0x2b38b027…eefc
0x34b655…2a6f
4 touches
1 conflict
0x810d42f0…2899
0x34b655…2a6f
4 touches
1 conflict
0x8aa96073…bba4
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 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity