← previous blocknext block →recent activity
Analyzing
Block #98,456,022
22 transactions · 21 stateful · 2026-08-23 10:33:23 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,456,022 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w010w111w313w015w416w517w018w119w121w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x227e5da3…9ccc
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x88ecacda…04c9
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcaced930…08b5
0x34b655…2a6f
4 touches
1 conflict
0xcaced930…08b6
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
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 0x227e5da302…f19ccc
Audit this contract →
← previous block·next block →recent activity