← previous blocknext block →recent activity
Analyzing
Block #108,444,265
16 transactions · 14 stateful · 2026-09-27 10:42:43 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,444,265 · 16 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
10w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x518b8dce…6d60
0x34b655…2a6f
4 touches
1 conflict
0x5c62fe6a…f144
0x34b655…2a6f
4 touches
1 conflict
0xdabae01b…82be
0x34b655…2a6f
4 touches
1 conflict
0xf3b3a6e9…8cd2
0x34b655…2a6f
4 touches
1 conflict
0x2a12f860…e6f3
0x34b655…2a6f
4 touches
1 conflict
0x213ee207…a151
0x34ae4d…3fc5
2 touches
0 conflicts
0x46279ae7…20dd
0x34ae4d…3fc5
2 touches
0 conflicts
0x53e50026…6d8c
0x34ae4d…3fc5
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 0x518b8dce2e…7e6d60
Audit this contract →
← previous block·next block →recent activity