← previous blocknext block →recent activity
Analyzing
Block #106,253,315
39 transactions · 35 stateful · 2026-09-19 18:52:00 UTC
Parallelism
80/100
Blocked
43%
Avg conflicts / tx
1.23
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,253,315 · 39 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w28w39w410w511w612w716w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe43b345e…a4e3
0x34b655…2a6f
16 touches
28 conflicts
0x48abf86b…223a
0x34b655…2a6f
12 touches
15 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001f
0x1b6862…e19c
10 touches
10 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0xa35509fa…5cb3
0x34b655…2a6f
10 touches
10 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
28 conflicts on slot 0xe43b345e79…6aa4e3
Audit this contract →
← previous block·next block →recent activity