← previous blocknext block →recent activity
Analyzing
Block #99,607,529
18 transactions · 18 stateful · 2026-08-27 11:56:07 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,607,529 · 18 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
2w04w15w17w08w09w110w112w214w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a12eed3…26b0
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x1f4e6c86…7789
0x34b655…2a6f
4 touches
1 conflict
0x3a106380…1d75
0x34b655…2a6f
4 touches
1 conflict
0x450f5a60…bf64
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x51cfbcbc…fa29
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
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 0x6a12eed3cf…2e26b0
Audit this contract →
← previous block·next block →recent activity