← previous blocknext block →recent activity
Analyzing
Block #106,252,299
11 transactions · 10 stateful · 2026-09-19 18:46:54 UTC
Parallelism
82/100
Blocked
10%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,252,299 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4073f47e…39e6
0x34b655…2a6f
4 touches
1 conflict
0xd1603130…9680
0x34b655…2a6f
4 touches
1 conflict
0x67a9f76d…0b84
0x34b655…2a6f
4 touches
1 conflict
0x67a9f76d…0b85
0x34b655…2a6f
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x4576762b…be2e
0x34b655…2a6f
2 touches
0 conflicts
0x6ca407b4…1edc
0x34b655…2a6f
2 touches
0 conflicts
0x6de748bb…eb4c
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x4073f47ec9…f139e6
Audit this contract →
← previous block·next block →recent activity