← previous blocknext block →recent activity
Analyzing
Block #74,353,908
13 transactions · 13 stateful · 2026-05-13 16:11:50 UTC
Parallelism
69/100
Blocked
46%
Avg conflicts / tx
0.77
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,353,908 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w16w010w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x801a6e57…d85c
0x34b655…2a6f
8 touches
6 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
6 touches
3 conflicts
0xfe48fc8c…b782
0x065c9d…c394
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x2f7781d6…e632
0x34b655…2a6f
4 touches
1 conflict
0xd8536f5c…1216
0xd32edf…ff58
3 touches
1 conflict
0xaeb5864c…7679
0x2a68ba…90c5
2 touches
0 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
6 conflicts on slot 0x801a6e5726…c1d85c
Audit this contract →
← previous block·next block →recent activity