← previous blocknext block →recent activity
Analyzing
Block #98,522,989
16 transactions · 16 stateful · 2026-08-23 16:15:12 UTC
Parallelism
69/100
Blocked
44%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,522,989 · 16 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
1w02w04w18w29w111w312w314w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1ef2821…0cf6
0x34b655…2a6f
8 touches
6 conflicts
0x344dd398…b320
0x34b655…2a6f
6 touches
3 conflicts
0x080c3a8a…3088
0x34b655…2a6f
4 touches
1 conflict
0x1867b653…e61b
0x34b655…2a6f
4 touches
1 conflict
0x3cb7ee74…b8a5
0x34b655…2a6f
4 touches
1 conflict
0x42e5184f…4e8b
0x34b655…2a6f
4 touches
1 conflict
0x45de70d9…e1dc
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xb1ef2821d9…560cf6
Audit this contract →
← previous block·next block →recent activity