← previous blocknext block →recent activity
Analyzing
Block #99,938,252
19 transactions · 17 stateful · 2026-08-28 15:49:17 UTC
Parallelism
84/100
Blocked
29%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,938,252 · 19 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
1w03w04w05w17w09w010w111w213w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdcc5622a…e1e2
0x34b655…2a6f
6 touches
3 conflicts
0x300807d1…7aa5
0x34b655…2a6f
6 touches
3 conflicts
0x83f3d320…fb59
0x34b655…2a6f
6 touches
3 conflicts
0xd814f518…f5b4
0x34b655…2a6f
6 touches
3 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5086c64a…28ba
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
3 conflicts on slot 0xdcc5622ae0…8de1e2
Audit this contract →
← previous block·next block →recent activity