← previous blocknext block →recent activity
Analyzing
Block #98,380,548
20 transactions · 19 stateful · 2026-08-23 04:13:34 UTC
Parallelism
70/100
Blocked
42%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,380,548 · 20 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
1w03w05w16w29w111w012w113w314w015w118w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa2945b7a…93fa
0x34b655…2a6f
8 touches
6 conflicts
0x8f84702c…c5f9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x4d42f16e…a6c8
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x05286dbb…4517
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
6 conflicts on slot 0xa2945b7a0d…0493fa
Audit this contract →
← previous block·next block →recent activity