← previous blocknext block →recent activity
Analyzing
Block #105,841,647
32 transactions · 30 stateful · 2026-09-18 08:18:53 UTC
Parallelism
84/100
Blocked
40%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,841,647 · 32 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
1w02w13w24w05w16w17w28w09w110w011w213w317w418w119w426w030w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe9d3448d…8000
0x34b655…2a6f
8 touches
6 conflicts
0xf8ec7381…bfbb
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x700a0b54…a84f
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xed863ec8…90dd
0x1b6862…e19c
4 touches
1 conflict
0x045532dd…4b7d
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 0xe9d3448d4a…ea8000
Audit this contract →
← previous block·next block →recent activity