← previous blocknext block →recent activity
Analyzing
Block #99,285,132
24 transactions · 24 stateful · 2026-08-26 08:47:58 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,285,132 · 24 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
4w05w17w011w113w015w116w219w020w121w022w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x467e524d…39c9
0x77d53b…8080
4 touches
1 conflict
0x85c42e7e…1a02
0x77d53b…8080
4 touches
1 conflict
0x85c42e7e…1a03
0x77d53b…8080
4 touches
1 conflict
0x85c42e7e…1a04
0x77d53b…8080
4 touches
1 conflict
0x86c68050…3174
0x77d53b…8080
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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity