← previous blocknext block →recent activity
Analyzing
Block #106,453,222
19 transactions · 18 stateful · 2026-09-20 11:38:05 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,453,222 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w211w112w213w014w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8bdb417a…f069
0x34b655…2a6f
8 touches
6 conflicts
0xa6b873a5…cffb
0x34b655…2a6f
6 touches
3 conflicts
0xb6ed530c…d450
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x9a291a56…9a9c
0x34b655…2a6f
4 touches
1 conflict
0x9f63b181…919d
0x34b655…2a6f
4 touches
1 conflict
0xa3ff1ab2…8ae3
0x34b655…2a6f
4 touches
1 conflict
0xa99b1dc9…6e86
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
6 conflicts on slot 0x8bdb417a40…5cf069
Audit this contract →
← previous block·next block →recent activity