← previous blocknext block →recent activity
Analyzing
Block #74,442,493
29 transactions · 26 stateful · 2026-05-14 02:01:34 UTC
Parallelism
66/100
Blocked
65%
Avg conflicts / tx
2.14
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #74,442,493 · 29 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w510w611w712w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0x62d080e9…4a7c
0x34b655…2a6f
8 touches
6 conflicts
0xf3981be5…2c47
0x34b655…2a6f
6 touches
3 conflicts
0x5675c293…17d9
0x34b655…2a6f
4 touches
1 conflict
0x57de3828…3fbb
0x34b655…2a6f
4 touches
1 conflict
0x7cbd466f…1700
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: 0xab35264b…1cfa38
36 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity