← previous blocknext block →recent activity
Analyzing
Block #105,608,519
35 transactions · 28 stateful · 2026-09-17 12:44:12 UTC
Parallelism
77/100
Blocked
57%
Avg conflicts / tx
1.26
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,608,519 · 35 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w38w49w511w113w119w632w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f84702c…c5f9
0x34b655…2a6f
16 touches
28 conflicts
0x00244932…d886
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xf90c6521…d8f0
0x34b655…2a6f
8 touches
6 conflicts
0xecf97be7…4ad9
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x4c20d376…0819
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
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
28 conflicts on slot 0x8f84702c8c…58c5f9
Audit this contract →
← previous block·next block →recent activity