← previous blocknext block →recent activity
Analyzing
Block #105,376,937
18 transactions · 18 stateful · 2026-09-16 17:18:36 UTC
Parallelism
72/100
Blocked
39%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,376,937 · 18 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
1w02w13w24w35w46w011w113w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xc40c1915…55ed
0x34b655…2a6f
10 touches
10 conflicts
0x6d787177…e955
0x34b655…2a6f
10 touches
10 conflicts
0x9210e826…1414
0x34b655…2a6f
10 touches
10 conflicts
0x30b29e9c…8cb9
0x34b655…2a6f
6 touches
3 conflicts
0xfba69cd9…52ab
0x34b655…2a6f
6 touches
3 conflicts
0x7c51d9aa…af39
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
10 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity