← previous blocknext block →recent activity
Analyzing
Block #98,018,612
33 transactions · 30 stateful · 2026-08-21 21:51:42 UTC
Parallelism
64/100
Blocked
53%
Avg conflicts / tx
1.94
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #98,018,612 · 33 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w17w08w19w010w111w214w215w017w118w324w425w526w627w728w829w930w1031w1132w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x737acb78…fce8
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xb409e204…89ac
0x34b655…2a6f
8 touches
6 conflicts
0x2930d7a8…ba40
0x34b655…2a6f
8 touches
6 conflicts
0x5e7da795…a150
0x34b655…2a6f
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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity