← previous blocknext block →recent activity
Analyzing
Block #105,933,259
29 transactions · 25 stateful · 2026-09-18 16:00:59 UTC
Parallelism
66/100
Blocked
64%
Avg conflicts / tx
1.72
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,933,259 · 29 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w17w28w39w410w512w613w717w820w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x3a429191…9cda
0x34b655…2a6f
6 touches
3 conflicts
0x197f6bcf…a23f
0x34b655…2a6f
4 touches
1 conflict
0x1b458e47…5ab5
0x34b655…2a6f
4 touches
1 conflict
0x1fc96968…a760
0x34b655…2a6f
4 touches
1 conflict
0x24c5620c…7ac5
0x34b655…2a6f
4 touches
1 conflict
0x31519d10…f76b
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
36 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity