← previous blocknext block →recent activity
Analyzing
Block #99,587,683
24 transactions · 23 stateful · 2026-08-27 10:14:00 UTC
Parallelism
83/100
Blocked
30%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,587,683 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w07w18w210w112w015w118w219w020w322w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x4761ac57…c42c
0xa6afd3…d132
4 touches
1 conflict
0xf8f1e808…a4fd
0x34b655…2a6f
4 touches
1 conflict
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x044ec7f8…a7c1
0x34b655…2a6f
4 touches
1 conflict
0x53c41998…7d52
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity