← previous blocknext block →recent activity
Analyzing
Block #99,196,719
20 transactions · 19 stateful · 2026-08-26 01:23:04 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.85
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,196,719 · 20 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
3w04w05w16w27w08w110w212w314w115w417w219w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea922228…ed63
0x34b655…2a6f
10 touches
10 conflicts
0x2202504e…fad0
0x34b655…2a6f
8 touches
6 conflicts
0x348fda08…7e96
0x065c9d…c394
6 touches
3 conflicts
0x961c0cd9…0937
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x631b4113…baa9
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5b6af007…0f35
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
10 conflicts on slot 0xea92222843…3aed63
Audit this contract →
← previous block·next block →recent activity