← previous blocknext block →recent activity
Analyzing
Block #108,567,332
15 transactions · 15 stateful · 2026-09-27 21:02:26 UTC
Parallelism
80/100
Blocked
27%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,567,332 · 15 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
6w07w18w09w110w211w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9674d680…261b
0x34b655…2a6f
4 touches
1 conflict
0x5060cdde…445d
0x34b655…2a6f
4 touches
1 conflict
0x7bd229ad…63b2
0x34b655…2a6f
4 touches
1 conflict
0x829f996c…a850
0x34b655…2a6f
4 touches
1 conflict
0xd4305f3b…7f3e
0x34b655…2a6f
4 touches
1 conflict
0xd7e4217d…7c6b
0x34b655…2a6f
4 touches
1 conflict
0xf5dc501b…831c
0x34b655…2a6f
4 touches
1 conflict
0x3b659361…89ef
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
1 conflict on slot 0x9674d68053…c5261b
Audit this contract →
← previous block·next block →recent activity