← previous blocknext block →recent activity
Analyzing
Block #99,162,361
17 transactions · 13 stateful · 2026-08-25 22:30:13 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,162,361 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w07w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x675c8b75…6e4f
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x024258fc…8163
0x34b655…2a6f
2 touches
0 conflicts
0x049e16b3…8059
0x34b655…2a6f
2 touches
0 conflicts
0x1e9e299e…713c
0x34b655…2a6f
2 touches
0 conflicts
0x20dbb179…625e
0x34b655…2a6f
2 touches
0 conflicts
0x21ecc707…2214
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x675c8b75ba…066e4f
Audit this contract →
← previous block·next block →recent activity