← previous blocknext block →recent activity
Analyzing
Block #99,160,320
28 transactions · 21 stateful · 2026-08-25 22:19:57 UTC
Parallelism
75/100
Blocked
67%
Avg conflicts / tx
1.46
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,160,320 · 28 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w47w58w610w617w521w022w123w224w325w426w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xf3d10975…0d07
0x34b655…2a6f
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
12 touches
15 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
12 touches
15 conflicts
0x36743f6f…476b
0x3bd359…433a
10 touches
10 conflicts
0xe31cf99d…cb66
0x754704…b603
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0x6d43ee99…bdd5
0x1b6862…e19c
8 touches
6 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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity