← previous blocknext block →recent activity
Analyzing
Block #74,428,052
25 transactions · 18 stateful · 2026-05-14 00:25:20 UTC
Parallelism
84/100
Blocked
39%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,428,052 · 25 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
1w02w13w24w36w120w022w123w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x35390095…1e5b
0xd32edf…ff58
7 touches
6 conflicts
0xbad68552…e6bf
0x34b655…2a6f
6 touches
3 conflicts
0xbbac368f…30db
0x34b655…2a6f
4 touches
1 conflict
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0x81955a0a…29ee
0x6657d1…8ccc
4 touches
1 conflict
0x999d5242…a337
0x6657d1…8ccc
4 touches
1 conflict
0xeeb8b7fc…24d6
0x6657d1…8ccc
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