← previous blocknext block →recent activity
Analyzing
Block #106,030,594
31 transactions · 19 stateful · 2026-09-19 00:11:02 UTC
Parallelism
87/100
Blocked
42%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,030,594 · 31 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
1w03w17w09w110w011w119w220w022w224w327w228w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd24f3ff8…ee48
0x34b655…2a6f
6 touches
3 conflicts
0xb6e0b4cf…e3a5
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x221a7b33…42e0
0xd32edf…ff58
5 touches
3 conflicts
0x187c5e31…4f1f
0x34b655…2a6f
4 touches
1 conflict
0x3d6c26e5…1b45
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity