← previous blocknext block →recent activity
Analyzing
Block #108,611,853
31 transactions · 27 stateful · 2026-09-28 00:46:33 UTC
Parallelism
87/100
Blocked
48%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,611,853 · 31 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
1w06w07w18w09w011w112w014w215w118w121w222w323w326w127w228w329w130w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7bd229ad…63b2
0x34b655…2a6f
6 touches
3 conflicts
0xf5dc501b…831c
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa535179d…f9dc
0x34b655…2a6f
6 touches
3 conflicts
0x8fa4ba1b…750c
0x34b655…2a6f
6 touches
3 conflicts
0x34db27d7…e422
0xd32edf…ff58
5 touches
3 conflicts
0x45ee8320…dbba
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 0x7bd229ade5…6b63b2
Audit this contract →
← previous block·next block →recent activity