← previous blocknext block →recent activity
Analyzing
Block #98,537,950
32 transactions · 29 stateful · 2026-08-23 17:33:01 UTC
Parallelism
84/100
Blocked
34%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,537,950 · 32 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
4w05w16w010w011w112w013w114w115w217w018w220w122w124w331w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x14cc77c7…69c4
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x86cea35b…bdff
0x34b655…2a6f
6 touches
3 conflicts
0xdc7b9eda…e616
0x34b655…2a6f
6 touches
3 conflicts
0xa9988419…9f45
0x34b655…2a6f
6 touches
3 conflicts
0xa02838a3…bc54
0x34b655…2a6f
6 touches
3 conflicts
0x2cb8837e…0f50
0x34b655…2a6f
6 touches
3 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 0x14cc77c78a…1369c4
Audit this contract →
← previous block·next block →recent activity