← previous blocknext block →recent activity
Analyzing
Block #106,040,076
22 transactions · 22 stateful · 2026-09-19 00:58:45 UTC
Parallelism
77/100
Blocked
45%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,040,076 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w19w110w212w213w315w416w317w018w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0001
0x2d82ac…5fd8
4 touches
1 conflict
0x8a2f9a36…fb4a
0x2d82ac…5fd8
4 touches
1 conflict
0x15e313f3…9aa1
0x34b655…2a6f
4 touches
1 conflict
0x315e07b8…9823
0x34b655…2a6f
4 touches
1 conflict
0x44521037…a0f0
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity