← previous blocknext block →recent activity
Analyzing
Block #99,616,700
20 transactions · 20 stateful · 2026-08-27 12:43:21 UTC
Parallelism
60/100
Blocked
45%
Avg conflicts / tx
1.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,616,700 · 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
2w03w14w08w19w210w311w414w515w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x231b3fa5…5466
0x34b655…2a6f
6 touches
3 conflicts
0x39ccd26a…4654
0x34b655…2a6f
6 touches
3 conflicts
0xb856d1a1…1f18
0x34b655…2a6f
4 touches
1 conflict
0xc40d0e10…b974
0x99c7a7…8bf0
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity