← previous blocknext block →recent activity
Analyzing
Block #99,481,531
17 transactions · 17 stateful · 2026-08-27 01:16:45 UTC
Parallelism
59/100
Blocked
59%
Avg conflicts / tx
1.65
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,481,531 · 17 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
1w02w13w04w15w26w17w08w19w211w312w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x100e0db7…6ae1
0x34b655…2a6f
12 touches
15 conflicts
0xfa09be5a…1e79
0x34b655…2a6f
10 touches
10 conflicts
0x310a7246…2dcb
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xac0b4a08…faae
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
15 conflicts on slot 0x100e0db74c…4a6ae1
Audit this contract →
← previous block·next block →recent activity