← previous blocknext block →recent activity
Analyzing
Block #106,187,534
18 transactions · 15 stateful · 2026-09-19 13:20:51 UTC
Parallelism
72/100
Blocked
67%
Avg conflicts / tx
0.89
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,187,534 · 18 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
1w03w14w26w09w111w212w313w414w115w416w317w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2a5cb78…d4c1
0x34b655…2a6f
8 touches
6 conflicts
0xd62f3741…b903
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x4d5053d1…3b7d
0x34b655…2a6f
6 touches
3 conflicts
0x9cf9008a…d826
0x34b655…2a6f
6 touches
3 conflicts
0xac0b4a08…faae
0x34b655…2a6f
6 touches
3 conflicts
0xb6ed511f…6b68
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 0xc2a5cb783d…3bd4c1
Audit this contract →
← previous block·next block →recent activity