← previous blocknext block →recent activity
Analyzing
Block #99,447,095
28 transactions · 27 stateful · 2026-08-26 22:23:21 UTC
Parallelism
75/100
Blocked
63%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,447,095 · 28 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w16w27w38w09w111w212w113w315w418w419w121w524w226w527w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x736b9166…5ea5
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x4635fb46…4cfd
0x34b655…2a6f
4 touches
1 conflict
0x48b3033c…3236
0x34b655…2a6f
4 touches
1 conflict
0x7e4547a3…c7d0
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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
10 conflicts on slot 0x736b916691…db5ea5
Audit this contract →
← previous block·next block →recent activity