← previous blocknext block →recent activity
Analyzing
Block #106,027,211
13 transactions · 13 stateful · 2026-09-18 23:54:00 UTC
Parallelism
77/100
Blocked
46%
Avg conflicts / tx
0.77
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,027,211 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w06w18w09w111w212w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69d2053b…935a
0x34b655…2a6f
6 touches
3 conflicts
0xbc8fb280…76a3
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x48828733…fd48
0x34b655…2a6f
4 touches
1 conflict
0x48b6f2c7…2ef7
0x34b655…2a6f
4 touches
1 conflict
0x6d5d1fb5…86a7
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
3 conflicts on slot 0x69d2053b7f…ea935a
Audit this contract →
← previous block·next block →recent activity