← previous blocknext block →recent activity
Analyzing
Block #74,361,458
17 transactions · 15 stateful · 2026-05-13 17:02:05 UTC
Parallelism
59/100
Blocked
47%
Avg conflicts / tx
1.06
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #74,361,458 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w213w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62d080e9…4a7c
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xaa3492db…3703
0x34b655…2a6f
8 touches
6 conflicts
0x55888ede…6745
0x34b655…2a6f
8 touches
6 conflicts
0x0711ec2d…d973
0x34b655…2a6f
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x75f6889e…7f1e
0x34b655…2a6f
6 touches
3 conflicts
0x908d4442…2c4b
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
10 conflicts on slot 0x62d080e928…5a4a7c
Audit this contract →
← previous block·next block →recent activity