← previous blocknext block →recent activity
Analyzing
Block #108,401,890
14 transactions · 13 stateful · 2026-09-27 07:09:26 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,401,890 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w18w19w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51e96b98…de36
0x34b655…2a6f
6 touches
3 conflicts
0xdabae01b…82be
0x34b655…2a6f
4 touches
1 conflict
0x5653d2ac…f31d
0x34b655…2a6f
4 touches
1 conflict
0x189fbafb…47ca
0x34b655…2a6f
4 touches
1 conflict
0xb8c8aca6…5da4
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x42744667…0b8a
0x34b655…2a6f
2 touches
0 conflicts
0x836094d7…2ce1
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
3 conflicts on slot 0x51e96b98d2…f7de36
Audit this contract →
← previous block·next block →recent activity