← previous blocknext block →recent activity
Analyzing
Block #99,180,720
22 transactions · 21 stateful · 2026-08-26 00:02:34 UTC
Parallelism
82/100
Blocked
48%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,180,720 · 22 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
1w03w05w16w07w18w113w114w216w217w218w119w121w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4bd60073…3d64
0x34b655…2a6f
6 touches
3 conflicts
0xce74d807…8716
0x34b655…2a6f
6 touches
3 conflicts
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0x3e49348b…9445
0x34b655…2a6f
4 touches
1 conflict
0x6efd1872…7582
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x9482a067…eba9
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
3 conflicts on slot 0x4bd60073bf…c33d64
Audit this contract →
← previous block·next block →recent activity