← previous blocknext block →recent activity
Analyzing
Block #106,790,024
30 transactions · 24 stateful · 2026-09-21 15:54:10 UTC
Parallelism
80/100
Blocked
54%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,790,024 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w39w110w011w013w414w517w418w121w123w124w526w429w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5eadd9ac…43cc
0x34b655…2a6f
6 touches
3 conflicts
0xc7e16629…11b7
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x8a02d049…f481
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xb87af72a…aef6
0x2a68ba…90c5
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
3 conflicts on slot 0x5eadd9acbd…6543cc
Audit this contract →
← previous block·next block →recent activity