← previous blocknext block →recent activity
Analyzing
Block #106,569,943
16 transactions · 16 stateful · 2026-09-20 21:25:31 UTC
Parallelism
56/100
Blocked
63%
Avg conflicts / tx
1.44
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,569,943 · 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
1w02w13w04w26w08w39w110w211w112w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6615a36…3cf0
0x34b655…2a6f
10 touches
10 conflicts
0xd7d44415…a1d3
0x34b655…2a6f
10 touches
10 conflicts
0xe283e878…7262
0x34b655…2a6f
6 touches
3 conflicts
0x310a7246…2dcb
0x34b655…2a6f
6 touches
3 conflicts
0x5d1ac445…5233
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0x872e51c8…ae2b
0x1b6862…e19c
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 0xc6615a36ef…7f3cf0
Audit this contract →
← previous block·next block →recent activity