← previous blocknext block →recent activity
Analyzing
Block #74,622,946
17 transactions · 14 stateful · 2026-05-14 22:10:16 UTC
Parallelism
53/100
Blocked
50%
Avg conflicts / tx
1.41
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #74,622,946 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w18w210w311w413w514w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xa91c899f…6ee3
0x34b655…2a6f
8 touches
6 conflicts
0xded5ec0c…f0fc
0x34b655…2a6f
6 touches
3 conflicts
0x7cab84dd…a441
0x34b655…2a6f
6 touches
3 conflicts
0x11cb770d…a0a3
0x34b655…2a6f
6 touches
3 conflicts
0x55b6a001…1e7a
0x34b655…2a6f
4 touches
1 conflict
0x7cbd466f…1700
0x34b655…2a6f
4 touches
1 conflict
0xacd10bf4…2244
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity