← previous blocknext block →recent activity
Analyzing
Block #104,198,291
25 transactions · 24 stateful · 2026-09-12 14:02:46 UTC
Parallelism
72/100
Blocked
54%
Avg conflicts / tx
1.4
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,198,291 · 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
1w02w03w14w26w19w010w113w214w315w418w519w622w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
14 touches
21 conflicts
0x5666db7d…5dc4
0x34b655…2a6f
10 touches
10 conflicts
0xe00608f8…edc2
0x34b655…2a6f
6 touches
3 conflicts
0x58737d82…26ba
0x34b655…2a6f
6 touches
3 conflicts
0x92664c6e…e3ca
0x34b655…2a6f
6 touches
3 conflicts
0x9a6bc012…7495
0x34b655…2a6f
6 touches
3 conflicts
0x9cf9008a…d826
0x34b655…2a6f
6 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