← previous blocknext block →recent activity
Analyzing
Block #74,332,427
15 transactions · 13 stateful · 2026-05-13 13:49:01 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,332,427 · 15 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
3w04w15w212w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62d080e9…4a7c
0x34b655…2a6f
8 touches
6 conflicts
0xa94cf3f4…554c
0x8d66a4…3095
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1aa
0x8d66a4…3095
6 touches
3 conflicts
0x908d4442…2c4b
0x34b655…2a6f
4 touches
1 conflict
0xea32922b…a5fc
0x34b655…2a6f
4 touches
1 conflict
0x0335ae80…8414
0x8d66a4…3095
4 touches
1 conflict
0x17cd1479…00bb
0x8d66a4…3095
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
6 conflicts on slot 0x62d080e928…5a4a7c
Audit this contract →
← previous block·next block →recent activity