← previous blocknext block →recent activity
Analyzing
Block #74,761,042
27 transactions · 21 stateful · 2026-05-15 13:31:59 UTC
Parallelism
85/100
Blocked
43%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,761,042 · 27 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
1w04w06w17w29w010w113w015w016w117w219w320w125w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e9e9bb8…360f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x631b4113…baa9
0x34b655…2a6f
6 touches
3 conflicts
0xeba9ca37…ebbb
0xd32edf…ff58
5 touches
3 conflicts
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0xb9868b52…c77f
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: Perpl
3 conflicts on slot 0x1e9e9bb815…c7360f
Audit this contract →
← previous block·next block →recent activity