← previous blocknext block →recent activity
Analyzing
Block #106,040,573
22 transactions · 19 stateful · 2026-09-19 01:01:15 UTC
Parallelism
86/100
Blocked
32%
Avg conflicts / tx
0.32
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,040,573 · 22 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
1w02w03w17w08w19w111w113w216w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5a233a4…fd0f
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xfcd7574f…a3a2
0x34b655…2a6f
6 touches
3 conflicts
0x20d91589…7a79
0x34b655…2a6f
4 touches
1 conflict
0x2249932e…474a
0x34b655…2a6f
4 touches
1 conflict
0x25fd5528…ff50
0x34b655…2a6f
4 touches
1 conflict
0x3f4b9f83…8493
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
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 0xa5a233a4a4…c6fd0f
Audit this contract →
← previous block·next block →recent activity