← previous blocknext block →recent activity
Analyzing
Block #108,396,256
16 transactions · 16 stateful · 2026-09-27 06:41:05 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,396,256 · 16 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
1w02w16w07w18w29w314w015w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe226a0be…c046
0x34b655…2a6f
10 touches
10 conflicts
0xbc5c1743…052c
0x34b655…2a6f
10 touches
10 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
8 touches
6 conflicts
0x40d6d1e9…131e
0x34b655…2a6f
8 touches
6 conflicts
0x5969523e…5191
0x34b655…2a6f
8 touches
6 conflicts
0x6d5d1fb5…86a7
0x34b655…2a6f
8 touches
6 conflicts
0x7006165a…df17
0x34b655…2a6f
8 touches
6 conflicts
0x9daafdf9…bb53
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0xe226a0be4d…4bc046
Audit this contract →
← previous block·next block →recent activity