← previous blocknext block →recent activity
Analyzing
Block #104,203,112
18 transactions · 16 stateful · 2026-09-12 14:27:17 UTC
Parallelism
67/100
Blocked
56%
Avg conflicts / tx
1.22
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,203,112 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w15w06w27w18w110w312w413w514w117w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ae5caa8…496f
0x34b655…2a6f
12 touches
15 conflicts
0x5666db7d…5dc4
0x34b655…2a6f
6 touches
3 conflicts
0xfb4f6c11…7103
0x34b655…2a6f
6 touches
3 conflicts
0x62023181…811e
0x34b655…2a6f
6 touches
3 conflicts
0xcd1306ad…f1b8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xaee82517…bb8a
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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
15 conflicts on slot 0x9ae5caa8a6…a0496f
Audit this contract →
← previous block·next block →recent activity