← previous blocknext block →recent activity
Analyzing
Block #105,403,105
19 transactions · 17 stateful · 2026-09-16 19:30:23 UTC
Parallelism
74/100
Blocked
65%
Avg conflicts / tx
1.11
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,403,105 · 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
1w02w03w15w27w38w19w212w313w314w415w217w418w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x851145…3f07
10 touches
10 conflicts
0x02ea2ac5…913f
0x851145…3f07
10 touches
10 conflicts
0x19e49883…3293
0x851145…3f07
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x67e4f554…12a3
0x851145…3f07
8 touches
6 conflicts
0x08d53462…97ef
0x34ae4d…3fc5
6 touches
3 conflicts
0x5a409e7f…09b6
0x34ae4d…3fc5
6 touches
3 conflicts
0x7a12283f…b18a
0x34ae4d…3fc5
6 touches
3 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: 0x851145ea…9f3f07
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity