← previous blocknext block →recent activity
Analyzing
Block #104,192,851
25 transactions · 22 stateful · 2026-09-12 13:35:02 UTC
Parallelism
72/100
Blocked
64%
Avg conflicts / tx
1.56
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,192,851 · 25 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
1w02w13w24w05w16w27w19w211w317w418w421w524w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x20282983…15f3
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x45de70d9…e1dc
0x34b655…2a6f
8 touches
6 conflicts
0xec37efb4…f355
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x361f4a1b…1f14
0x34b655…2a6f
6 touches
3 conflicts
0x290a2c36…7f84
0xd32edf…ff58
5 touches
3 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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity