← previous blocknext block →recent activity
Analyzing
Block #106,551,820
15 transactions · 14 stateful · 2026-09-20 19:54:18 UTC
Parallelism
53/100
Blocked
43%
Avg conflicts / tx
1.4
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,551,820 · 15 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
4w06w17w28w39w410w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9733a5bf…f0fc
0x34b655…2a6f
14 touches
21 conflicts
0x1d9867ad…6d9a
0x34b655…2a6f
10 touches
10 conflicts
0x23769ebc…c8ed
0x34b655…2a6f
6 touches
3 conflicts
0xba1edffb…323e
0x34b655…2a6f
6 touches
3 conflicts
0xbaf6ed88…c179
0x34b655…2a6f
4 touches
1 conflict
0x172b0de5…980b
0x34b655…2a6f
4 touches
1 conflict
0x1b25f260…c429
0x34b655…2a6f
4 touches
1 conflict
0x3b6e959d…158f
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
21 conflicts on slot 0x9733a5bf3e…e4f0fc
Audit this contract →
← previous block·next block →recent activity