← previous blocknext block →recent activity
Analyzing
Block #108,923,367
21 transactions · 17 stateful · 2026-09-29 02:58:03 UTC
Parallelism
67/100
Blocked
35%
Avg conflicts / tx
0.62
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,923,367 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w318w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c29ecd5…58b6
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
8 touches
6 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
6 touches
3 conflicts
0x86bf7578…c38f
0x34b655…2a6f
6 touches
3 conflicts
0x88fc2a68…3918
0x34b655…2a6f
6 touches
3 conflicts
0xab2b11cd…7e41
0x34b655…2a6f
6 touches
3 conflicts
0xada087b9…4aca
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x4c29ecd55a…1058b6
Audit this contract →
← previous block·next block →recent activity