← previous blocknext block →recent activity
Analyzing
Block #74,252,602
22 transactions · 18 stateful · 2026-05-13 04:58:06 UTC
Parallelism
77/100
Blocked
50%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,252,602 · 22 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
1w02w15w08w010w111w212w313w114w419w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x768cffcd…2648
0x34b655…2a6f
10 touches
10 conflicts
0x0d0b2509…074d
0x3bd359…433a
8 touches
6 conflicts
0xe6455d1f…1029
0x754704…b603
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x71e96b74…abe9
0x34b655…2a6f
6 touches
3 conflicts
0x6c6f37ba…c20c
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xa7283528…fe5b
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
10 conflicts on slot 0x768cffcdb0…d12648
Audit this contract →
← previous block·next block →recent activity