← previous blocknext block →recent activity
Analyzing
Block #99,986,921
21 transactions · 16 stateful · 2026-08-28 19:54:32 UTC
Parallelism
90/100
Blocked
31%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,986,921 · 21 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
3w04w18w09w112w013w114w016w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0e00683…e335
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x3f81bcfb…2905
0x40c49f…2af0
4 touches
1 conflict
0x7c7ac75f…4b64
0x40c49f…2af0
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0db949a4…cf38
0x34b655…2a6f
4 touches
1 conflict
0x6ca15e14…7be8
0x34b655…2a6f
4 touches
1 conflict
0x97420b44…a2a8
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
1 conflict on slot 0xe0e0068315…bbe335
Audit this contract →
← previous block·next block →recent activity