← previous blocknext block →recent activity
Analyzing
Block #99,877,287
16 transactions · 16 stateful · 2026-08-28 10:42:03 UTC
Parallelism
81/100
Blocked
19%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,877,287 · 16 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
2w06w111w013w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x80c79cb7…91d0
0x34b655…2a6f
4 touches
1 conflict
0x30ae635d…5e67
0x34b655…2a6f
2 touches
0 conflicts
0x6c71d878…ef64
0x34b655…2a6f
2 touches
0 conflicts
0x6c91cadf…709c
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 0x326a02b5c5…5c8dad
Audit this contract →
← previous block·next block →recent activity