← previous blocknext block →recent activity
Analyzing
Block #74,210,328
19 transactions · 16 stateful · 2026-05-13 00:16:59 UTC
Parallelism
47/100
Blocked
56%
Avg conflicts / tx
2.11
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #74,210,328 · 19 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w010w111w212w313w414w515w616w717w818w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xa91c899f…6ee3
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0x1b159f3d…9163
0x34b655…2a6f
10 touches
10 conflicts
0xbb1747e2…f78b
0x34b655…2a6f
8 touches
6 conflicts
0xee2bb5dd…99f2
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xe5e7089a…fb91
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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity