← previous blocknext block →recent activity
Analyzing
Block #108,309,612
14 transactions · 14 stateful · 2026-09-26 23:25:05 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,309,612 · 14 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
1w08w110w011w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x742ef9fa…7f17
0x34b655…2a6f
4 touches
1 conflict
0x7bd229ad…63b2
0x34b655…2a6f
4 touches
1 conflict
0xf5dc501b…831c
0x34b655…2a6f
4 touches
1 conflict
0x3a663e9a…a9c4
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9c5
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9c6
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9c7
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9c8
0x508254…98bd
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 0x742ef9fa47…747f17
Audit this contract →
← previous block·next block →recent activity