← previous blocknext block →recent activity
Analyzing
Block #99,993,996
16 transactions · 16 stateful · 2026-08-28 20:30:09 UTC
Parallelism
75/100
Blocked
44%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,993,996 · 16 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
1w02w14w05w16w07w110w211w212w313w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f04fe6a…5c0f
0x34b655…2a6f
8 touches
6 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
6 touches
3 conflicts
0xc45e4fb5…7cc3
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x9ff4ca89…6115
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xf6deafb5…5c25
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 0x8f04fe6adc…0e5c0f
Audit this contract →
← previous block·next block →recent activity