← previous blocknext block →recent activity
Analyzing
Block #74,761,073
20 transactions · 16 stateful · 2026-05-15 13:32:12 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,761,073 · 20 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
1w02w04w16w28w315w117w018w1
- 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
4 touches
1 conflict
0xf853eb8e…4027
0x34b655…2a6f
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0x62d080e9…4a7c
0x34b655…2a6f
4 touches
1 conflict
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x68faa0b9…14af
0x368ee5…7ca4
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: 0xab35264b…1cfa38
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity