← previous blocknext block →recent activity
Analyzing
Block #98,568,799
63 transactions · 57 stateful · 2026-08-23 20:14:13 UTC
Parallelism
81/100
Blocked
61%
Avg conflicts / tx
2.24
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #98,568,799 · 63 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
2w03w17w08w110w011w112w213w314w415w516w617w718w819w920w1022w123w224w225w343w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xbb3f3c…e046
22 touches
55 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
16 touches
28 conflicts
0x92385428…6941
0x34b655…2a6f
16 touches
28 conflicts
0x886db264…846e
0x34b655…2a6f
12 touches
15 conflicts
0xec1f8387…c83d
0x34b655…2a6f
10 touches
10 conflicts
0x9c2e6ea0…9df8
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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: 0xbb3f3cb7…74e046
55 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity