← previous blocknext block →recent activity
Analyzing
Block #103,039,850
19 transactions · 17 stateful · 2026-09-08 12:30:40 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
1.47
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #103,039,850 · 19 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
2w03w16w27w38w410w011w112w513w618w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25180879…8191
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xc8cadee4…1bef
0x34b655…2a6f
8 touches
6 conflicts
0x1cd9bcd1…f26c
0x34b655…2a6f
8 touches
6 conflicts
0x55192654…91fe
0x34b655…2a6f
6 touches
3 conflicts
0x502b3ee1…7f7c
0x34b655…2a6f
6 touches
3 conflicts
0xbfb4b02a…4b47
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 0x25180879df…1c8191
Audit this contract →
← previous block·next block →recent activity