← previous blocknext block →recent activity
Analyzing
Block #106,944,457
22 transactions · 21 stateful · 2026-09-22 04:51:30 UTC
Parallelism
68/100
Blocked
43%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,944,457 · 22 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
1w02w03w19w010w111w112w214w015w117w318w419w520w021w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66b19827…9edc
0x34b655…2a6f
10 touches
10 conflicts
0x91cd366d…5cea
0x34b655…2a6f
8 touches
6 conflicts
0xe22ab637…7a8e
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd192f4ed…d7ec
0x34b655…2a6f
6 touches
3 conflicts
0xdf64e5e6…75e8
0x34b655…2a6f
6 touches
3 conflicts
0xfce5d77b…45c1
0x34b655…2a6f
6 touches
3 conflicts
0x9375a764…dca1
0x34b655…2a6f
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 0x66b198273e…f79edc
Audit this contract →
← previous block·next block →recent activity