← previous blocknext block →recent activity
Analyzing
Block #106,800,906
17 transactions · 15 stateful · 2026-09-21 16:48:57 UTC
Parallelism
59/100
Blocked
60%
Avg conflicts / tx
1.35
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,800,906 · 17 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
1w02w13w26w17w28w39w410w511w613w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49cc564b…6e2d
0x34b655…2a6f
12 touches
15 conflicts
0x9edb7ad7…8d56
0x34b655…2a6f
10 touches
10 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
10 touches
10 conflicts
0x3cc3cee1…372a
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xba5743c7…21c1
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x3cf50d44…961b
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
15 conflicts on slot 0x49cc564bec…3c6e2d
Audit this contract →
← previous block·next block →recent activity