← previous blocknext block →recent activity
Analyzing
Block #99,811,281
16 transactions · 15 stateful · 2026-08-28 05:08:39 UTC
Parallelism
69/100
Blocked
47%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,811,281 · 16 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
2w04w05w16w18w210w211w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4c703ab…f8cf
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xb31eb7d3…64eb
0xa6afd3…d132
4 touches
1 conflict
0x7c29a0cf…8f8c
0x34b655…2a6f
4 touches
1 conflict
0x820d7282…6c34
0x34b655…2a6f
4 touches
1 conflict
0x9ecf942d…fdb7
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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 0xb4c703ab76…fdf8cf
Audit this contract →
← previous block·next block →recent activity