← previous blocknext block →recent activity
Analyzing
Block #98,678,571
10 transactions · 9 stateful · 2026-08-24 05:45:57 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,678,571 · 10 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
1w02w13w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89ac61bf…9443
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x00d67843…2809
0x34b655…2a6f
2 touches
0 conflicts
0x0128552f…ca34
0x34b655…2a6f
2 touches
0 conflicts
0x14cc77c7…69c4
0x34b655…2a6f
2 touches
0 conflicts
0x1a922fed…d138
0x34b655…2a6f
2 touches
0 conflicts
0x1c2f0c4c…9bca
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x89ac61bf64…6b9443
Audit this contract →
← previous block·next block →recent activity