← previous blocknext block →recent activity
Analyzing
Block #104,165,893
23 transactions · 21 stateful · 2026-09-12 11:18:24 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,165,893 · 23 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
1w02w18w010w113w214w315w417w419w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8ac39e10…2cf8
0x34b655…2a6f
12 touches
15 conflicts
0x5d6da397…6c5c
0x34b655…2a6f
12 touches
15 conflicts
0x5fde4971…aac9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x8f63f383…6eda
0x34b655…2a6f
6 touches
3 conflicts
0x0630c2e5…b5de
0x34b655…2a6f
4 touches
1 conflict
0x45de70d9…e1dc
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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
15 conflicts on slot 0x8ac39e106d…ab2cf8
Audit this contract →
← previous block·next block →recent activity