← previous blocknext block →recent activity
Analyzing
Block #104,204,687
14 transactions · 12 stateful · 2026-09-12 14:35:18 UTC
Parallelism
79/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #104,204,687 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w011w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc853be2d…b18f
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x14f03197…2dba
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0x0deb5804…40c6
0x34b655…2a6f
4 touches
1 conflict
0x5fc06aef…c10d
0x34b655…2a6f
2 touches
0 conflicts
0x85a88798…f85e
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xc853be2d22…5eb18f
Audit this contract →
← previous block·next block →recent activity