← previous blocknext block →recent activity
Analyzing
Block #99,080,656
16 transactions · 14 stateful · 2026-08-25 15:38:52 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,080,656 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
0w09w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
4 touches
1 conflict
0x246320e8…37d8
0x34b655…2a6f
2 touches
0 conflicts
0x37c0660b…e0bf
0x34b655…2a6f
2 touches
0 conflicts
0x4977d235…a8f6
0x34b655…2a6f
2 touches
0 conflicts
0x4ab47306…f0c8
0x34b655…2a6f
2 touches
0 conflicts
0x52df67cf…f77b
0x34b655…2a6f
2 touches
0 conflicts
0x605e358e…dc99
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity