← previous blocknext block →recent activity
Analyzing
Block #99,277,881
27 transactions · 26 stateful · 2026-08-26 08:11:29 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
0.96
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,277,881 · 27 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
1w02w14w25w06w111w212w313w414w015w117w018w119w220w321w422w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
10 touches
10 conflicts
0xaede47b1…aff1
0xe52b14…7230
10 touches
10 conflicts
0xaede47b1…afef
0xe52b14…7230
10 touches
10 conflicts
0xa6843be4…4b57
0xd32edf…ff58
9 touches
10 conflicts
0x476027d8…4833
0xe52b14…7230
8 touches
10 conflicts
0x6cc5ca07…1020
0xe52b14…7230
8 touches
6 conflicts
0x0b0c2e8d…c1b8
0xe52b14…7230
8 touches
6 conflicts
0x11258774…9892
0x2a68ba…90c5
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: 0xe52b1424…bb7230
10 conflicts on slot 0xf79df061c7…91e005
Audit this contract →
← previous block·next block →recent activity