← previous blocknext block →recent activity
Analyzing
Block #108,497,108
16 transactions · 15 stateful · 2026-09-27 15:08:44 UTC
Parallelism
56/100
Blocked
60%
Avg conflicts / tx
1.75
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,497,108 · 16 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
1w02w13w24w05w16w27w38w410w314w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c29ecd5…58b6
0x34b655…2a6f
14 touches
21 conflicts
0x26471102…35f9
0x34b655…2a6f
10 touches
10 conflicts
0x280aaa58…1c52
0x34b655…2a6f
10 touches
10 conflicts
0x16d77246…bac5
0x34b655…2a6f
10 touches
10 conflicts
0x40d6d1e9…131e
0x34b655…2a6f
10 touches
10 conflicts
0x7006165a…df17
0x34b655…2a6f
10 touches
10 conflicts
0xad601853…1d2a
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 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
21 conflicts on slot 0x4c29ecd55a…1058b6
Audit this contract →
← previous block·next block →recent activity