← previous blocknext block →recent activity
Analyzing
Block #99,616,189
17 transactions · 16 stateful · 2026-08-27 12:40:42 UTC
Parallelism
59/100
Blocked
44%
Avg conflicts / tx
1.35
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,616,189 · 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
4w05w17w28w39w410w512w615w016w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3cd6dc90…823e
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xef3f5637…f47c
0x34b655…2a6f
8 touches
6 conflicts
0xdc7b9eda…e616
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x30ae635d…5e67
0x34b655…2a6f
6 touches
3 conflicts
0x91311109…4687
0x34b655…2a6f
6 touches
3 conflicts
0x72083f0d…082a
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
15 conflicts on slot 0x3cd6dc907a…e1823e
Audit this contract →
← previous block·next block →recent activity