← previous blocknext block →recent activity
Analyzing
Block #99,084,893
23 transactions · 22 stateful · 2026-08-25 16:00:15 UTC
Parallelism
78/100
Blocked
41%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,084,893 · 23 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
1w02w06w17w09w212w113w315w119w120w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0x4e58deff…c5d0
0x34b655…2a6f
4 touches
1 conflict
0x5a6d0315…e515
0x34b655…2a6f
4 touches
1 conflict
0x5cb2ad15…0483
0x34b655…2a6f
4 touches
1 conflict
0x757dd9d2…0fb5
0x34b655…2a6f
4 touches
1 conflict
0x75f36d60…8556
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity