← previous blocknext block →recent activity
Analyzing
Block #104,194,600
17 transactions · 17 stateful · 2026-09-12 13:44:00 UTC
Parallelism
76/100
Blocked
24%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #104,194,600 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w06w110w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d6da397…6c5c
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xf961041a…3632
0x34b655…2a6f
6 touches
3 conflicts
0xfc2493d3…6898
0x34b655…2a6f
4 touches
1 conflict
0x5666db7d…5dc4
0x34b655…2a6f
4 touches
1 conflict
0xa33be62c…2c6a
0x34b655…2a6f
4 touches
1 conflict
0xa7c7b00e…bc2e
0x34b655…2a6f
4 touches
1 conflict
0xb8632b42…d1a3
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
6 conflicts on slot 0x5d6da39762…d36c5c
Audit this contract →
← previous block·next block →recent activity