← previous blocknext block →recent activity
Analyzing
Block #106,379,717
32 transactions · 30 stateful · 2026-09-20 05:28:06 UTC
Parallelism
72/100
Blocked
50%
Avg conflicts / tx
1.53
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,379,717 · 32 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w319w423w524w625w726w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x168458e1…ca7e
0x34b655…2a6f
16 touches
28 conflicts
0xdd77da90…6df4
0x34b655…2a6f
8 touches
6 conflicts
0xe283e878…7262
0x34b655…2a6f
8 touches
6 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
8 touches
6 conflicts
0xf217fa05…207f
0x34b655…2a6f
8 touches
6 conflicts
0x54f7f60f…43cc
0x34b655…2a6f
8 touches
6 conflicts
0x5ff01ee9…5a45
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0x168458e176…45ca7e
Audit this contract →
← previous block·next block →recent activity