← previous blocknext block →recent activity
Analyzing
Block #104,878,009
21 transactions · 18 stateful · 2026-09-14 23:27:35 UTC
Parallelism
76/100
Blocked
50%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,878,009 · 21 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
4w05w16w29w010w111w212w314w315w016w119w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81716ce9…095f
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x03500bec…db28
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xb550abea…2729
0x34b655…2a6f
6 touches
3 conflicts
0x07405812…0d81
0x34b655…2a6f
4 touches
1 conflict
0x1e2c6318…f7e7
0x34b655…2a6f
4 touches
1 conflict
0x0145aa28…106b
0x34b655…2a6f
4 touches
1 conflict
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 0x81716ce924…61095f
Audit this contract →
← previous block·next block →recent activity