← previous blocknext block →recent activity
Analyzing
Block #74,566,066
18 transactions · 14 stateful · 2026-05-14 15:49:42 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
0.72
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,566,066 · 18 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
2w03w14w25w38w010w011w115w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xff57dec4…6482
0x34b655…2a6f
6 touches
3 conflicts
0xad2bb81f…4d6b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3b2d25d4…fb40
0x34b655…2a6f
4 touches
1 conflict
0x764f2d09…bc43
0x34b655…2a6f
4 touches
1 conflict
0xadac4a86…c2bc
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
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity