← previous blocknext block →recent activity
Analyzing
Block #74,228,902
15 transactions · 12 stateful · 2026-05-13 02:20:32 UTC
Parallelism
73/100
Blocked
50%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,228,902 · 15 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
1w02w13w27w08w112w313w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x768cffcd…2648
0x34b655…2a6f
6 touches
3 conflicts
0x6dbf943f…6f51
0xd32edf…ff58
5 touches
3 conflicts
0x65b4bfb0…8e6c
0x065c9d…c394
4 touches
1 conflict
0xcf3283ba…c9fa
0x065c9d…c394
4 touches
1 conflict
0xf823e97f…2ee6
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
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
3 conflicts on slot 0x768cffcdb0…d12648
Audit this contract →
← previous block·next block →recent activity