← previous blocknext block →recent activity
Analyzing
Block #104,983,817
17 transactions · 14 stateful · 2026-09-15 08:20:00 UTC
Parallelism
65/100
Blocked
36%
Avg conflicts / tx
0.47
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,983,817 · 17 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
5w06w17w28w012w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x115183e2…1a53
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xa7ecbbe7…f713
0x34b655…2a6f
6 touches
3 conflicts
0x1f396cee…862f
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x59dccbd8…2bf6
0x34b655…2a6f
4 touches
1 conflict
0x5bcd8b85…8710
0x34b655…2a6f
4 touches
1 conflict
0x886ec04d…db35
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
3 conflicts on slot 0x115183e280…5c1a53
Audit this contract →
← previous block·next block →recent activity