← previous blocknext block →recent activity
Analyzing
Block #105,402,997
16 transactions · 16 stateful · 2026-09-16 19:29:51 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
0.69
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,402,997 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w310w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c4fbcbc…d11d
0x34b655…2a6f
8 touches
6 conflicts
0x8726b27c…9a04
0x34b655…2a6f
6 touches
3 conflicts
0xda15cc7b…5b64
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x7cfedb52…2eec
0xd32edf…ff58
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xed863ec8…90dc
0x1b6862…e19c
4 touches
1 conflict
0x2697123c…8526
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 0x1c4fbcbcdc…23d11d
Audit this contract →
← previous block·next block →recent activity