← previous blocknext block →recent activity
Analyzing
Block #108,366,656
16 transactions · 15 stateful · 2026-09-27 04:12:08 UTC
Parallelism
63/100
Blocked
40%
Avg conflicts / tx
0.69
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,366,656 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w07w19w110w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1679b727…0208
0x34b655…2a6f
6 touches
3 conflicts
0xffa25fc2…fe39
0x34b655…2a6f
6 touches
3 conflicts
0xdd77da90…6df4
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x3da6ec2b…b836
0x34b655…2a6f
4 touches
1 conflict
0xa2b54fc1…51d2
0x34b655…2a6f
4 touches
1 conflict
0xb6de158b…6fdd
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 0x1679b7275f…f90208
Audit this contract →
← previous block·next block →recent activity