← previous blocknext block →recent activity
Analyzing
Block #98,452,034
20 transactions · 17 stateful · 2026-08-23 10:13:14 UTC
Parallelism
80/100
Blocked
35%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,452,034 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w110w211w012w116w017w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xbe9c719b…2939
0xd32edf…ff58
5 touches
3 conflicts
0x88e92ec7…696d
0x34b655…2a6f
4 touches
1 conflict
0xeb5b61a2…b2bc
0x34b655…2a6f
4 touches
1 conflict
0x8e80434a…a96d
0x0555e3…2b9c
2 touches
0 conflicts
0x4a7516b9…efd5
0x065c9d…c394
2 touches
0 conflicts
0x46cb45de…a566
0x188d58…ea8e
2 touches
0 conflicts
0x46cb45de…a567
0x188d58…ea8e
2 touches
0 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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity