← previous blocknext block →recent activity
Analyzing
Block #105,682,861
23 transactions · 17 stateful · 2026-09-17 18:58:27 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,682,861 · 23 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
3w04w16w09w110w216w217w322w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xf80ee985…43d5
0x34b655…2a6f
4 touches
1 conflict
0x08c5d8d8…c7c1
0x34b655…2a6f
4 touches
1 conflict
0x0a809ce1…7894
0x34b655…2a6f
4 touches
1 conflict
0x2b362527…5809
0x34b655…2a6f
4 touches
1 conflict
0x3d93ad2c…e747
0x34b655…2a6f
4 touches
1 conflict
0x429c8b35…0f5c
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 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity