← previous blocknext block →recent activity
Analyzing
Block #106,453,039
16 transactions · 15 stateful · 2026-09-20 11:37:10 UTC
Parallelism
69/100
Blocked
60%
Avg conflicts / tx
1.13
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,453,039 · 16 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
1w02w13w24w08w19w110w211w312w413w314w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea6f9041…e46d
0x34b655…2a6f
10 touches
10 conflicts
0x8d664414…3344
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0x17a7f697…dcb4
0x1b6862…e19c
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001b
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
10 conflicts on slot 0xea6f904158…85e46d
Audit this contract →
← previous block·next block →recent activity