← previous blocknext block →recent activity
Analyzing
Block #99,446,544
15 transactions · 15 stateful · 2026-08-26 22:20:34 UTC
Parallelism
60/100
Blocked
40%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,446,544 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w07w38w411w514w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d442736…1b47
0x34b655…2a6f
6 touches
3 conflicts
0xe97d54c5…ef6f
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x07b5c6c6…886a
0x1b6862…e19c
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 0x7d442736ac…dc1b47
Audit this contract →
← previous block·next block →recent activity