← previous blocknext block →recent activity
Analyzing
Block #98,653,951
45 transactions · 35 stateful · 2026-08-24 03:37:32 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
1.87
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #98,653,951 · 45 txs across 15 waves · depth 15
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
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w07w18w09w010w011w113w014w216w018w219w321w422w523w630w231w132w733w836w138w843w1344w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
20 touches
45 conflicts
0xc824469a…6425
0x34b655…2a6f
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xe22455da…1ce1
0x34b655…2a6f
12 touches
15 conflicts
0x261cbea7…e35e
0x34b655…2a6f
6 touches
3 conflicts
0x386d08f4…5a01
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35d
0x34b655…2a6f
6 touches
3 conflicts
0x48b13e5e…3c2a
0x34b655…2a6f
6 touches
3 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
45 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity