← previous blocknext block →recent activity
Analyzing
Block #105,857,904
13 transactions · 13 stateful · 2026-09-18 09:40:51 UTC
Parallelism
62/100
Blocked
38%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,857,904 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w27w18w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08e6e52f…3d80
0x34b655…2a6f
6 touches
3 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0xba1edffb…323e
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x931975c2…b7b3
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 0x08e6e52f32…3b3d80
Audit this contract →
← previous block·next block →recent activity