← previous blocknext block →recent activity
Analyzing
Block #106,110,401
18 transactions · 16 stateful · 2026-09-19 06:52:39 UTC
Parallelism
78/100
Blocked
31%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,110,401 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w112w316w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x75f36d60…8556
0x34b655…2a6f
8 touches
6 conflicts
0x22187aaf…c0d5
0x34b655…2a6f
8 touches
6 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
8 touches
6 conflicts
0x3c9b10c1…d791
0x34b655…2a6f
6 touches
3 conflicts
0x634015e1…0b09
0x34b655…2a6f
6 touches
3 conflicts
0x6d5d1fb5…86a7
0x34b655…2a6f
6 touches
3 conflicts
0x7a3d5e6f…7864
0x34b655…2a6f
6 touches
3 conflicts
0x7eb3ae1e…a1a3
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0x75f36d60ac…458556
Audit this contract →
← previous block·next block →recent activity