← previous blocknext block →recent activity
Analyzing
Block #74,788,998
32 transactions · 24 stateful · 2026-05-15 16:39:03 UTC
Parallelism
88/100
Blocked
42%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,788,998 · 32 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
1w03w04w05w18w110w211w012w013w119w223w325w127w028w129w230w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
8 touches
6 conflicts
0x388f889f…a655
0x34b655…2a6f
7 touches
6 conflicts
0x801a6e57…d85c
0x34b655…2a6f
6 touches
3 conflicts
0xb9a3472b…e37a
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0000
0x63e48b…53f2
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity