← previous blocknext block →recent activity
Analyzing
Block #106,539,266
36 transactions · 31 stateful · 2026-09-20 18:51:08 UTC
Parallelism
89/100
Blocked
39%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,539,266 · 36 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w06w17w28w39w013w115w117w018w126w228w029w331w134w135w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6cbc1a2…9f44
0x34b655…2a6f
8 touches
6 conflicts
0x735a86cd…b64d
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xbaf6ed88…c179
0x34b655…2a6f
6 touches
3 conflicts
0xcc8faac2…c766
0x065c9d…c394
6 touches
3 conflicts
0xcd5c0ecb…4b5f
0x34b655…2a6f
6 touches
3 conflicts
0x21d22421…0b7a
0x34b655…2a6f
4 touches
1 conflict
0x3643741b…109c
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 0xa6cbc1a209…7c9f44
Audit this contract →
← previous block·next block →recent activity