← previous blocknext block →recent activity
Analyzing
Block #105,583,184
19 transactions · 17 stateful · 2026-09-17 10:36:40 UTC
Parallelism
74/100
Blocked
53%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,583,184 · 19 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
1w02w14w25w37w010w111w212w113w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c51d9aa…af39
0x34b655…2a6f
8 touches
6 conflicts
0x818e1296…f4d7
0x34b655…2a6f
8 touches
6 conflicts
0x6a2154b8…48e5
0x34b655…2a6f
8 touches
6 conflicts
0xca608d0c…f23b
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x6d43ee99…bdd5
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x08b13d26…42e5
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 0x7c51d9aa1a…7faf39
Audit this contract →
← previous block·next block →recent activity