← previous blocknext block →recent activity
Analyzing
Block #74,353,936
36 transactions · 23 stateful · 2026-05-13 16:12:01 UTC
Parallelism
86/100
Blocked
43%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,353,936 · 36 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w29w010w122w023w124w225w326w432w133w134w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0xafd59af5…5257
0xc8689a…ee79
8 touches
6 conflicts
0x20ac0567…c954
0x34b655…2a6f
8 touches
6 conflicts
0x2484cc15…5afc
0x34b655…2a6f
8 touches
6 conflicts
0x38c47502…1005
0x34b655…2a6f
8 touches
6 conflicts
0x6f2e60dc…e661
0x34b655…2a6f
8 touches
6 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
8 touches
6 conflicts
0xbfca3cd0…5023
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
10 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity