← previous blocknext block →recent activity
Analyzing
Block #104,149,039
13 transactions · 12 stateful · 2026-09-12 09:52:46 UTC
Parallelism
54/100
Blocked
42%
Avg conflicts / tx
1.31
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,149,039 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w17w28w310w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4350838…fa7c
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc7954a60…d294
0x34b655…2a6f
6 touches
3 conflicts
0x1bb56de3…732e
0x34b655…2a6f
6 touches
3 conflicts
0x705a9a1a…db08
0x34b655…2a6f
6 touches
3 conflicts
0xe00608f8…edc2
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7746704d…9928
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 0xf43508387b…6ffa7c
Audit this contract →
← previous block·next block →recent activity