← previous blocknext block →recent activity
Analyzing
Block #105,366,108
23 transactions · 21 stateful · 2026-09-16 16:24:06 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,366,108 · 23 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
4w05w16w08w010w011w012w113w014w115w219w120w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xce935849…b0c0
0x34b655…2a6f
4 touches
1 conflict
0xd0caf939…ce30
0x34b655…2a6f
4 touches
1 conflict
0xd16ffb3d…fe01
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity