← previous blocknext block →recent activity
Analyzing
Block #99,780,699
25 transactions · 21 stateful · 2026-08-28 02:33:33 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,780,699 · 25 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
8w09w110w211w012w114w217w321w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53c41998…7d52
0x34b655…2a6f
8 touches
6 conflicts
0x631b4113…baa9
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xdfb56da3…2576
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xcbbd3473…0bff
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xa605468c…1bfc
0x2b46c0…1669
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
6 conflicts on slot 0x53c41998b8…357d52
Audit this contract →
← previous block·next block →recent activity