← previous blocknext block →recent activity
Analyzing
Block #98,984,936
62 transactions · 41 stateful · 2026-08-25 07:30:51 UTC
Parallelism
76/100
Blocked
56%
Avg conflicts / tx
1.97
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #98,984,936 · 62 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
1w02w04w15w018w219w120w021w022w123w225w140w342w444w345w250w453w654w755w856w958w1159w1260w1361w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0xea02471d…1542
0x34b655…2a6f
24 touches
66 conflicts
0xf3d10975…0d07
0x34b655…2a6f
22 touches
55 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
18 touches
36 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0xadac4a86…c2bc
0x34b655…2a6f
9 touches
10 conflicts
0xbad68552…e6bf
0x34b655…2a6f
8 touches
6 conflicts
0xd40bddc1…773c
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
66 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity