← previous blocknext block →recent activity
Analyzing
Block #99,614,841
15 transactions · 14 stateful · 2026-08-27 12:33:35 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,614,841 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w19w210w011w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba6ef0ed…bd43
0x34b655…2a6f
6 touches
3 conflicts
0xeabd47a7…c286
0x851145…3f07
6 touches
3 conflicts
0xc6174640…66c9
0x851145…3f07
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x014e90b3…470f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x742436a7…c4d4
0x34b655…2a6f
4 touches
1 conflict
0xc1da8f73…484c
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
3 conflicts on slot 0xba6ef0ed24…ecbd43
Audit this contract →
← previous block·next block →recent activity