← previous blocknext block →recent activity
Analyzing
Block #108,402,192
10 transactions · 9 stateful · 2026-09-27 07:10:58 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,402,192 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7bd229ad…63b2
0x34b655…2a6f
4 touches
1 conflict
0x15d2f566…9194
0x34b655…2a6f
4 touches
1 conflict
0xf5dc501b…831c
0x34b655…2a6f
4 touches
1 conflict
0x481db2dd…cc35
0x34b655…2a6f
4 touches
1 conflict
0x4073f47e…39e6
0x34b655…2a6f
2 touches
0 conflicts
0x74e485b1…d380
0x34b655…2a6f
2 touches
0 conflicts
0x75f108dc…f5a7
0x34b655…2a6f
2 touches
0 conflicts
0x9f90e86c…ece7
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x7bd229ade5…6b63b2
Audit this contract →
← previous block·next block →recent activity