← previous blocknext block →recent activity
Analyzing
Block #99,505,174
33 transactions · 31 stateful · 2026-08-27 03:15:47 UTC
Parallelism
79/100
Blocked
58%
Avg conflicts / tx
1.12
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,505,174 · 33 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
1w04w05w17w08w09w110w111w214w215w316w117w218w319w321w425w526w127w628w431w332w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd22d0fc…64fd
0x34b655…2a6f
10 touches
10 conflicts
0xd9722304…6ed0
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x2bd1251f…b327
0x34b655…2a6f
4 touches
1 conflict
0x4b53c962…f39c
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 0xbd22d0fc04…0464fd
Audit this contract →
← previous block·next block →recent activity