← previous blocknext block →recent activity
Analyzing
Block #99,246,978
7 transactions · 7 stateful · 2026-08-26 05:35:56 UTC
Parallelism
57/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,246,978 · 7 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b6af007…0f35
0x34b655…2a6f
4 touches
1 conflict
0xd2dfd9bc…3eec
0x34b655…2a6f
4 touches
1 conflict
0x93c4b345…b915
0x34b655…2a6f
4 touches
1 conflict
0xe4dd9449…31cf
0x34b655…2a6f
4 touches
1 conflict
0x15bb783d…9b7d
0x34b655…2a6f
2 touches
0 conflicts
0x1c831236…a132
0x34b655…2a6f
2 touches
0 conflicts
0x23b82c26…9aa1
0x34b655…2a6f
2 touches
0 conflicts
0x295780b7…d2d1
0x34b655…2a6f
2 touches
0 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: Perpl
1 conflict on slot 0x5b6af0070f…160f35
Audit this contract →
← previous block·next block →recent activity