← previous blocknext block →recent activity
Analyzing
Block #99,856,026
17 transactions · 17 stateful · 2026-08-28 08:54:53 UTC
Parallelism
71/100
Blocked
24%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,856,026 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w08w19w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x20c391ea…c0e6
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xdb8288e3…7979
0x34b655…2a6f
8 touches
6 conflicts
0x97112b59…f61f
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x72083f0d…082a
0x34b655…2a6f
4 touches
1 conflict
0xb54c8ced…5b8c
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
6 conflicts on slot 0x20c391ea95…5cc0e6
Audit this contract →
← previous block·next block →recent activity