← previous blocknext block →recent activity
Analyzing
Block #74,765,548
51 transactions · 37 stateful · 2026-05-15 14:02:12 UTC
Parallelism
73/100
Blocked
59%
Avg conflicts / tx
1.78
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #74,765,548 · 51 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w08w09w110w211w012w120w021w323w024w125w226w327w428w529w630w731w832w933w1038w239w342w344w145w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
24 touches
66 conflicts
0x388e001a…7e04
0x34b655…2a6f
10 touches
10 conflicts
0xf853eb8e…4027
0x34b655…2a6f
10 touches
10 conflicts
0x65b89141…61de
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x443a3e47…f4a4
0x065c9d…c394
8 touches
6 conflicts
0x57de3828…3fbb
0x34b655…2a6f
8 touches
6 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
8 touches
6 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
66 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity