← previous blocknext block →recent activity
Analyzing
Block #99,867,436
20 transactions · 18 stateful · 2026-08-28 09:52:27 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
1.4
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,867,436 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w19w210w312w413w515w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x6fce7a05…d778
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x54216be0…ba5a
0x34b655…2a6f
6 touches
3 conflicts
0x8981c6c0…df37
0x34b655…2a6f
6 touches
3 conflicts
0x3cb7ee74…b8a5
0x34b655…2a6f
6 touches
3 conflicts
0x30f879d2…e39a
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity