← previous blocknext block →recent activity
Analyzing
Block #106,040,018
28 transactions · 23 stateful · 2026-09-19 00:58:27 UTC
Parallelism
86/100
Blocked
43%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,040,018 · 28 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
1w02w04w05w06w17w29w115w017w018w119w220w121w124w225w326w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98568c43…ff4e
0x34b655…2a6f
8 touches
6 conflicts
0xb0a4e112…f855
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xcb45d9d6…cb83
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x23a320fb…cbd7
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 0x98568c43d7…70ff4e
Audit this contract →
← previous block·next block →recent activity