← previous blocknext block →recent activity
Analyzing
Block #98,851,890
31 transactions · 27 stateful · 2026-08-24 20:21:29 UTC
Parallelism
74/100
Blocked
52%
Avg conflicts / tx
1.1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #98,851,890 · 31 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w29w310w413w515w617w018w119w220w329w630w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x11b69a7e…334e
0x01bff4…1071
8 touches
6 conflicts
0x00000000…0036
0x35a73b…6042
8 touches
6 conflicts
0xaf831072…51d5
0x69a5f9…2fef
8 touches
6 conflicts
0xaf831072…51d6
0x69a5f9…2fef
8 touches
6 conflicts
0xaf831072…51dc
0x69a5f9…2fef
8 touches
6 conflicts
0x2ef1d89b…196d
0x754704…b603
8 touches
6 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
15 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity