← previous blocknext block →recent activity
Analyzing
Block #98,732,704
21 transactions · 13 stateful · 2026-08-24 10:21:32 UTC
Parallelism
90/100
Blocked
31%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,732,704 · 21 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w06w115w116w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x065ff70b…356d
0x40c49f…2af0
4 touches
1 conflict
0x23b9ceb1…4d1a
0x40c49f…2af0
4 touches
1 conflict
0x3f81bcfb…2905
0x40c49f…2af0
4 touches
1 conflict
0xb6be7f7d…56b2
0x40c49f…2af0
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
1 conflict on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity