← previous blocknext block →recent activity
Analyzing
Block #99,357,020
24 transactions · 22 stateful · 2026-08-26 14:49:39 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,357,020 · 24 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
1w02w14w010w012w113w216w318w123w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x27b6010e…e4aa
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0ee24619…c0db
0x34b655…2a6f
4 touches
1 conflict
0x20e46e7f…1e46
0x34b655…2a6f
4 touches
1 conflict
0x47d60193…c6b6
0x34b655…2a6f
4 touches
1 conflict
0x676f9f01…a8ac
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
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 0x27b6010e94…34e4aa
Audit this contract →
← previous block·next block →recent activity