← previous blocknext block →recent activity
Analyzing
Block #104,847,542
20 transactions · 18 stateful · 2026-09-14 20:54:12 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,847,542 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w110w011w112w214w317w418w019w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf96d1661…31ce
0x34b655…2a6f
6 touches
3 conflicts
0xa35509fa…5cb3
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xb856d1a1…1f18
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x7725a03d…bc15
0x34b655…2a6f
6 touches
3 conflicts
0xf06fce24…887d
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
3 conflicts on slot 0xf96d16611c…c431ce
Audit this contract →
← previous block·next block →recent activity