← previous blocknext block →recent activity
Analyzing
Block #107,450,133
14 transactions · 13 stateful · 2026-09-23 23:17:11 UTC
Parallelism
64/100
Blocked
54%
Avg conflicts / tx
0.93
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,450,133 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w011w112w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1b2
0x37db7f…ec7b
10 touches
10 conflicts
0x8a35acfb…d1b1
0x37db7f…ec7b
6 touches
3 conflicts
0x91ecc547…33f2
0x1b6862…e19c
4 touches
1 conflict
0x60c7a9f8…9886
0x34b655…2a6f
4 touches
1 conflict
0xa3d78e5e…bb33
0x34b655…2a6f
4 touches
1 conflict
0xb94a2ed9…d989
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xfc8c9734…8019
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: 0x37db7fbf…3eec7b
10 conflicts on slot 0x8a35acfbc1…6bd1b2
Audit this contract →
← previous block·next block →recent activity