← previous blocknext block →recent activity
Analyzing
Block #106,953,645
17 transactions · 14 stateful · 2026-09-22 05:37:45 UTC
Parallelism
76/100
Blocked
50%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,953,645 · 17 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
1w02w03w04w16w18w110w111w212w314w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e32cf94…887e
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…004f
0x80c745…7210
4 touches
1 conflict
0x4e58deff…c5d0
0x34b655…2a6f
4 touches
1 conflict
0x58234472…c591
0x34b655…2a6f
4 touches
1 conflict
0xc1da8f73…484c
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf8abaacb…b80d
0x34b655…2a6f
4 touches
1 conflict
0xfaf89f45…ced6
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 0x7e32cf9449…c4887e
Audit this contract →
← previous block·next block →recent activity