← previous blocknext block →recent activity
Analyzing
Block #104,200,992
18 transactions · 16 stateful · 2026-09-12 14:16:30 UTC
Parallelism
50/100
Blocked
63%
Avg conflicts / tx
2.44
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #104,200,992 · 18 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w37w38w411w512w413w616w717w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ccfe55c…de03
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0xa5ff384c…3a25
0x34b655…2a6f
10 touches
10 conflicts
0x5581159e…0a5c
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x5666db7d…5dc4
0x34b655…2a6f
6 touches
3 conflicts
0x1408e7c7…f324
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
28 conflicts on slot 0x4ccfe55c0b…fbde03
Audit this contract →
← previous block·next block →recent activity