← previous blocknext block →recent activity
Analyzing
Block #99,353,123
30 transactions · 21 stateful · 2026-08-26 14:30:00 UTC
Parallelism
80/100
Blocked
52%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,353,123 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w012w115w016w017w118w219w320w422w125w126w227w328w429w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
10 touches
10 conflicts
0x23529e13…6f25
0x34b655…2a6f
6 touches
3 conflicts
0x6f132c01…cdcc
0x34b655…2a6f
6 touches
3 conflicts
0x0d435849…e51f
0x34b655…2a6f
4 touches
1 conflict
0x18c53a40…8bd0
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6266e26a…96ee
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcd
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
10 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity