← previous blocknext block →recent activity
Analyzing
Block #104,876,577
20 transactions · 20 stateful · 2026-09-14 23:20:23 UTC
Parallelism
80/100
Blocked
45%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #104,876,577 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w07w09w110w111w112w113w214w016w117w318w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc844ab5…4c6d
0x34b655…2a6f
6 touches
3 conflicts
0xc99c3069…b799
0x34b655…2a6f
6 touches
3 conflicts
0xbeb716e1…2f28
0x34b655…2a6f
6 touches
3 conflicts
0xac389ba9…8b45
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004f
0x80c745…7210
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x4611acd1…c536
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
3 conflicts on slot 0xcc844ab542…814c6d
Audit this contract →
← previous block·next block →recent activity