← previous blocknext block →recent activity
Analyzing
Block #99,667,761
14 transactions · 13 stateful · 2026-08-27 17:01:24 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,667,761 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w36w213w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22db2187…cb6b
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xd9fcbb8d…e3ef
0x34b655…2a6f
4 touches
1 conflict
0x832b8321…3e2f
0x34b655…2a6f
4 touches
1 conflict
0x8d419d46…d789
0x34b655…2a6f
4 touches
1 conflict
0xbbc06cbf…9342
0x34b655…2a6f
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
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
6 conflicts on slot 0x22db2187ac…2acb6b
Audit this contract →
← previous block·next block →recent activity