← previous blocknext block →recent activity
Analyzing
Block #99,957,387
19 transactions · 19 stateful · 2026-08-28 17:25:44 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.74
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,957,387 · 19 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
1w02w03w05w16w29w110w212w313w114w317w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7ce83b1…2c96
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x39fc983b…2a6f
0x34b655…2a6f
4 touches
1 conflict
0x5a548af5…0eb0
0x34b655…2a6f
4 touches
1 conflict
0x5bdffe1c…2a9e
0x34b655…2a6f
4 touches
1 conflict
0x5da59c2b…d7b2
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0xb5922b6d…5ecc
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 0xb7ce83b1b6…352c96
Audit this contract →
← previous block·next block →recent activity