← previous blocknext block →recent activity
Analyzing
Block #99,953,069
30 transactions · 26 stateful · 2026-08-28 17:03:59 UTC
Parallelism
83/100
Blocked
42%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,953,069 · 30 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
1w02w03w14w16w07w19w110w212w315w216w417w227w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x408db73d…6e90
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x74e485b1…d380
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x9513aafb…bb7f
0x34b655…2a6f
4 touches
1 conflict
0xbb97db90…4c93
0xc8689a…ee79
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity