← previous blocknext block →recent activity
Analyzing
Block #97,478,422
19 transactions · 17 stateful · 2026-08-20 00:06:36 UTC
Parallelism
79/100
Blocked
47%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,478,422 · 19 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
2w04w16w07w18w09w110w111w213w214w015w118w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6737ee07…9978
0x34b655…2a6f
6 touches
3 conflicts
0xea1d91a3…b583
0x34b655…2a6f
4 touches
1 conflict
0xea79e6d3…68ad
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x103de0…bb55
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x6737ee07d3…1e9978
Audit this contract →
← previous block·next block →recent activity