← previous blocknext block →recent activity
Analyzing
Block #73,751,125
23 transactions · 19 stateful · 2026-05-10 21:13:31 UTC
Parallelism
57/100
Blocked
63%
Avg conflicts / tx
2.13
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #73,751,125 · 23 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
1w02w14w06w17w28w39w418w519w620w721w822w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5de96bd3…c60c
0x34b655…2a6f
20 touches
45 conflicts
0x99120c08…ee84
0x34b655…2a6f
18 touches
36 conflicts
0xedb848fe…6534
0x34b655…2a6f
12 touches
15 conflicts
0xfac43f12…b842
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xf853eb8e…4027
0x34b655…2a6f
10 touches
10 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
8 touches
6 conflicts
0xac8e97a0…8426
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
45 conflicts on slot 0x5de96bd34a…ecc60c
Audit this contract →
← previous block·next block →recent activity