← previous blocknext block →recent activity
Analyzing
Block #96,022,679
46 transactions · 45 stateful · 2026-08-14 21:18:49 UTC
Parallelism
70/100
Blocked
71%
Avg conflicts / tx
2.74
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #96,022,679 · 46 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w06w07w18w29w210w311w312w413w414w515w516w617w619w427w929w830w1034w136w937w238w343w1144w1245w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c188934…158e
0x34b655…2a6f
18 touches
36 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
14 touches
21 conflicts
0xec7d120d…7084
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0002
0x103de0…bb55
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x7de57974…f5ba
0x34b655…2a6f
8 touches
6 conflicts
0x3464bbc5…a323
0xa6afd3…d132
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
36 conflicts on slot 0x4c18893450…c5158e
Audit this contract →
← previous block·next block →recent activity