← previous blocknext block →recent activity
Analyzing
Block #106,419,980
13 transactions · 11 stateful · 2026-09-20 08:50:43 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,419,980 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w08w19w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d017b93…8081
0x34b655…2a6f
4 touches
1 conflict
0xaf7f09cd…1068
0x40c49f…2af0
4 touches
1 conflict
0xf171f918…801d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x26a4c9bf…ccfa
0x40c49f…2af0
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x53e50026…6d8c
0x34ae4d…3fc5
2 touches
0 conflicts
0x7f4a8466…f2cc
0x34ae4d…3fc5
2 touches
0 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: Perpl
1 conflict on slot 0x9d017b9313…e88081
Audit this contract →
← previous block·next block →recent activity