← previous blocknext block →recent activity
Analyzing
Block #105,846,232
23 transactions · 22 stateful · 2026-09-18 08:42:06 UTC
Parallelism
70/100
Blocked
32%
Avg conflicts / tx
0.87
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,846,232 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
13w014w115w216w317w318w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69bf73eb…fe40
0x34b655…2a6f
8 touches
6 conflicts
0xb7ce83b1…2c96
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xd6113c0f…0a4b
0x34b655…2a6f
8 touches
6 conflicts
0x5bdffe1c…2a9e
0x34b655…2a6f
8 touches
6 conflicts
0x82f1ed07…ff68
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x7b67f6cf…0aab
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
6 conflicts on slot 0x69bf73eb51…5dfe40
Audit this contract →
← previous block·next block →recent activity