← previous blocknext block →recent activity
Analyzing
Block #108,419,622
30 transactions · 25 stateful · 2026-09-27 08:38:41 UTC
Parallelism
83/100
Blocked
32%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,419,622 · 30 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
1w07w08w113w020w122w223w324w325w426w027w129w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba5214c2…44eb
0x34b655…2a6f
8 touches
6 conflicts
0x6b267bdf…b173
0x34b655…2a6f
8 touches
6 conflicts
0x899b65d2…c8cd
0x34b655…2a6f
6 touches
3 conflicts
0xf30b9357…2e1e
0x34b655…2a6f
6 touches
3 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x31d88d27…7617
0x34b655…2a6f
4 touches
1 conflict
0x3fa1fac4…826c
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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
6 conflicts on slot 0xba5214c250…c144eb
Audit this contract →
← previous block·next block →recent activity