← previous blocknext block →recent activity
Analyzing
Block #99,878,863
20 transactions · 19 stateful · 2026-08-28 10:49:59 UTC
Parallelism
80/100
Blocked
26%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,878,863 · 20 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
1w04w05w18w09w112w114w218w019w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c29ecd5…58b6
0x34b655…2a6f
8 touches
6 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
8 touches
6 conflicts
0x0baf5ede…b815
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x2b093939…9083
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x1032f16c…a9b1
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 0x4c29ecd55a…1058b6
Audit this contract →
← previous block·next block →recent activity