← previous blocknext block →recent activity
Analyzing
Block #99,985,980
57 transactions · 52 stateful · 2026-08-28 19:49:46 UTC
Parallelism
81/100
Blocked
65%
Avg conflicts / tx
1.58
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #99,985,980 · 57 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w06w07w18w09w110w211w312w413w514w615w716w817w119w220w121w225w226w330w132w334w239w346w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x451e482b…7e7d
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x1e168c8b…6945
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x6f132c01…cdcc
0x34b655…2a6f
6 touches
3 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: 0xf5b5f7f8…a36d70
36 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity