← previous blocknext block →recent activity
Analyzing
Block #98,413,814
35 transactions · 31 stateful · 2026-08-23 07:00:56 UTC
Parallelism
66/100
Blocked
65%
Avg conflicts / tx
2.23
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #98,413,814 · 35 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
1w02w14w05w16w27w38w09w110w011w115w116w117w220w224w225w326w427w528w629w731w932w1034w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0x92385428…6941
0x34b655…2a6f
20 touches
45 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
20 touches
45 conflicts
0x886db264…846e
0x34b655…2a6f
18 touches
36 conflicts
0x15b3ea9f…ef46
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0002
0xbb3f3c…e046
8 touches
6 conflicts
0x60d6a0c9…1430
0x34b655…2a6f
6 touches
3 conflicts
0xaa179075…fdee
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
55 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity