← previous blocknext block →recent activity
Analyzing
Block #99,255,843
22 transactions · 19 stateful · 2026-08-26 06:20:33 UTC
Parallelism
77/100
Blocked
37%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,255,843 · 22 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
2w03w04w17w08w113w014w217w218w320w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb86a86fb…2f7e
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x4c29ecd5…58b6
0x34b655…2a6f
4 touches
1 conflict
0x5c1b956d…14d3
0x34b655…2a6f
4 touches
1 conflict
0x5c455afd…ce06
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
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
3 conflicts on slot 0xb86a86fbc3…cb2f7e
Audit this contract →
← previous block·next block →recent activity