← previous blocknext block →recent activity
Analyzing
Block #98,532,713
66 transactions · 58 stateful · 2026-08-23 17:05:51 UTC
Parallelism
80/100
Blocked
66%
Avg conflicts / tx
2.12
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #98,532,713 · 66 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w06w17w28w09w110w211w012w123w124w228w134w139w541w142w244w645w747w948w1054w656w358w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
24 touches
66 conflicts
0xc824469a…6425
0x34b655…2a6f
22 touches
55 conflicts
0xd66696e0…0842
0x34b655…2a6f
14 touches
21 conflicts
0xb0d9297f…aa4b
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x45de70d9…e1dc
0x34b655…2a6f
10 touches
10 conflicts
0x8590b692…b267
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…641f
0x34b655…2a6f
10 touches
10 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
66 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity