← previous blocknext block →recent activity
Analyzing
Block #106,950,287
18 transactions · 16 stateful · 2026-09-22 05:20:51 UTC
Parallelism
72/100
Blocked
44%
Avg conflicts / tx
0.89
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,950,287 · 18 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
1w04w06w17w211w312w413w114w216w017w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebef1329…2bf0
0x34b655…2a6f
10 touches
10 conflicts
0x2f48aa0f…fbf0
0x34b655…2a6f
8 touches
6 conflicts
0x1f396cee…862f
0x34b655…2a6f
6 touches
3 conflicts
0x9375a764…dca1
0x34b655…2a6f
6 touches
3 conflicts
0xd1b40f29…9b9d
0x34b655…2a6f
6 touches
3 conflicts
0x18cf3003…51d1
0x065c9d…c394
6 touches
3 conflicts
0xc953c572…34b1
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
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 0xebef132916…0c2bf0
Audit this contract →
← previous block·next block →recent activity