← previous blocknext block →recent activity
Analyzing
Block #99,329,868
20 transactions · 19 stateful · 2026-08-26 12:32:59 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
1.3
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,329,868 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w19w110w211w313w215w016w217w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd895ee0b…d301
0x34b655…2a6f
6 touches
3 conflicts
0x79347b24…9fba
0x34b655…2a6f
6 touches
3 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity