← previous blocknext block →recent activity
Analyzing
Block #105,643,334
21 transactions · 18 stateful · 2026-09-17 15:39:29 UTC
Parallelism
81/100
Blocked
44%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,643,334 · 21 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
2w03w14w05w16w27w315w216w319w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x0e9210b8…64ae
0x34b655…2a6f
8 touches
6 conflicts
0x86bd79a5…1f48
0x34b655…2a6f
6 touches
3 conflicts
0x22badbc6…4c24
0x34b655…2a6f
4 touches
1 conflict
0x5f76b8ee…ecfe
0x34b655…2a6f
4 touches
1 conflict
0x6b68679f…a232
0x34b655…2a6f
4 touches
1 conflict
0x75f36d60…8556
0x34b655…2a6f
4 touches
1 conflict
0x88fc2a68…3918
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