← previous blocknext block →recent activity
Analyzing
Block #106,008,328
10 transactions · 10 stateful · 2026-09-18 22:18:59 UTC
Parallelism
80/100
Blocked
30%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,008,328 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b995497…5e06
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x159cff26…7665
0x34b655…2a6f
4 touches
1 conflict
0x85eb1316…bb9e
0x34b655…2a6f
4 touches
1 conflict
0x753972af…5df6
0x40c49f…2af0
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x7f4a8466…f2cc
0x34ae4d…3fc5
2 touches
0 conflicts
0x524f0872…0d12
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x6b99549708…465e06
Audit this contract →
← previous block·next block →recent activity