← previous blocknext block →recent activity
Analyzing
Block #106,944,024
16 transactions · 16 stateful · 2026-09-22 04:49:19 UTC
Parallelism
56/100
Blocked
56%
Avg conflicts / tx
1.56
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,944,024 · 16 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
1w02w13w24w05w16w17w28w39w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfa2d197a…0dbb
0x34b655…2a6f
14 touches
21 conflicts
0x8d5fc820…1750
0x34b655…2a6f
14 touches
21 conflicts
0x1f396cee…862f
0x34b655…2a6f
8 touches
6 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0x3a3097d7…2ab7
0x1b6862…e19c
6 touches
3 conflicts
0x704a8131…bbe8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
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
21 conflicts on slot 0xfa2d197a8f…940dbb
Audit this contract →
← previous block·next block →recent activity